471,354 Members | 1,181 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,354 software developers and data experts.

useUnsafeHeaderParsing(WebRequest) in Win app.config

I use WebRequest.Create/WebRequest.GetResponse to handle HTTP request in a
VS2003 project. I got HTTP violation exception on some of the machine. So I
did the research, and found to put <useUnsafeHeaderParsing ="true"> in
app.config can fix the problem.

But the app.config cause problem on other machines which work fine without
application config file. The exception is <Unrecognized attribute
'useUnsafeHeaderParsing'>. I use framework1.1 on this machine. Install
framework2.0 did not fix the problem.

Because my application will distribute to other users machine, the users is
not IT professional. How could I fix the problem with a simple installation,
other than manually change configuration on end user machine?

Thanks.

Dec 30 '05 #1
2 3898
I believe from checking the documentation that useUnsafeHeaderParsing is new
in .NET 2.0. You might try taking any of the offending control or other
characters in your post that may be causing this and converting them to their
"HTML - safe" entity references instead.
--Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"MikeZ" wrote:
I use WebRequest.Create/WebRequest.GetResponse to handle HTTP request in a
VS2003 project. I got HTTP violation exception on some of the machine. So I
did the research, and found to put <useUnsafeHeaderParsing ="true"> in
app.config can fix the problem.

But the app.config cause problem on other machines which work fine without
application config file. The exception is <Unrecognized attribute
'useUnsafeHeaderParsing'>. I use framework1.1 on this machine. Install
framework2.0 did not fix the problem.

Because my application will distribute to other users machine, the users is
not IT professional. How could I fix the problem with a simple installation,
other than manually change configuration on end user machine?

Thanks.

Dec 30 '05 #2
Peter,

Why some of the machines didn't throw exception on useUnsafeHeaderParsing?
These machine only have Framework 1.0 and 1.1 installed.

I searched newsgroup, some guys have the same problem, but I cannot reconize
German. Something related to Framework 1.1 SP1.
Jan 3 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.