ansaurus

Question

Answer 1

A:

As this is semi-random, the second option in this blog post may help.

CodeByMoonlight 2009-10-15 14:57:45

Thanks for your answer! Do you mean the hardcoded CSS values? I've definitely not put anything like that in our stylesheets, and we're not using any "packaged contronl" that outputs this kinds of things (like BasicDatePicker does, for example). If that's not what you meant, sorry if I didn't understand

Daniel Magliola 2009-10-15 15:27:01

CodeByMoonlight 2009-10-15 15:43:00

Daniel Magliola 2009-10-15 16:23:37

Answer 2

A:

Since the URL appears to be manipulated, it looks like it is a bug in a proxy software. Maybe you can find patterns in the requesting IP Ranges to identify certain proxies or ISPs.

However, that does not really explain the constant IE6 UserAgent (unless the proxy screws that up too). It could be one of the many IE bugs (e.g. gzip issues, Missing 4k Bug, etc.) but those usually break much more than just lowercasing an URL and remove one character. You could temporarily turn off gzip to see if it has any effect.

Here is a question with similar symptoms and my answer includes links to some of the IE bugs.

Josef 2009-10-18 08:51:56

Answer 3

A:

You could try setting a fixed machineKey in your web.config file. For this you can use a machineKey generator or generate your own:

<system.web>
    <machineKey
        validationKey='SOME KEY'
        decryptionKey='OTHER KEY'
        validation='SHA1'/>
</system.web>

Darin Dimitrov 2009-10-18 09:06:31

don't have a server farm, this is a single server. The problem is that IE6 (or some proxy, or something, although if it's a proxy, I wonder why I only get IE6 UA's) is screwing up the content it sends to the server, either the URL or the POST data, it's not the server not being able to "decrypt" it.

Daniel Magliola 2009-10-19 22:48:04

Answer 4

A:

If you've already set a fixed MachineKey in your web.config, then this issue is most likely proxies messing up the requests. We get it with some of our IE6 users as well, and I've also seen where proxies turn & into & in the querystring (which is incorrect).

Nicholas H 2009-10-19 01:51:48

Answer 5

+1 A:

Just guessing here, but I had a similar problem with special characters being removed/substituted when I used IIS 7 to run some sites. Turned out to be IIS's "security feature" - its rules are in "urlscan.ini". Maybe this will help.

DV 2009-10-19 06:07:58

Answer 6

+2 A:

We were seeing similar errors with ScriptResource.axd and Invalid Viewstate exceptions. Eventually I found this post:

Error : /ScriptResource.axd : Invalid viewstate.

Which indicated a bug in IE (and possibly other browsers) where an invalid DOCTYPE of XHTML causes the browser to make an incorrect request to ScriptResource.axd. We solved the problem by changing the XHTML DOCTYPE to the HTML5 doctype and removing the xmlns attribute from the html tag. Our pages were not XHTML compliant anyway.

From:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;
<html xmlns="http://www.w3.org/1999/xhtml" >

To:

<!DOCTYPE html>
<html>

Jeff Widmer 2009-10-20 08:59:00

Answer 7

A:

You could check:

-doctype (does it match the data you're sending? IE6 is picky)

-character set

jvenema 2009-10-20 20:59:52

ansaurus

tags:

views:

answers:

ASP.Net: IE6 making invalid requests

related questions