MattBrooks: How do you know it never shows up as an error to the user? My guess is that it does, but it's usually in somewhat subtle ways. For instance, if the link to WebResource.axd is bad, it won't load in that supporting JavaScript. No error will
necessarily be immediately obvious to the user from that problem...but some associated functionality, such as script validation may now fail.
It looks like most people are having problems with 4K being dropped from the html stream somewhere. Can you verify if that's what you're seeing as well?
We are actually seeing this problem in more places than we originally anticipated, but we weren't aware of them because the only time it was reported back to the server was when a url was bad (such as WebResource.axd), and then a request came back for that
URL.
beska_miltar
0 Points
5 Posts
Re: Corrupted WebResource.axd url parameters
May 19, 2009 01:58 PM|LINK
MattBrooks: How do you know it never shows up as an error to the user? My guess is that it does, but it's usually in somewhat subtle ways. For instance, if the link to WebResource.axd is bad, it won't load in that supporting JavaScript. No error will necessarily be immediately obvious to the user from that problem...but some associated functionality, such as script validation may now fail.
It looks like most people are having problems with 4K being dropped from the html stream somewhere. Can you verify if that's what you're seeing as well?
We are actually seeing this problem in more places than we originally anticipated, but we weren't aware of them because the only time it was reported back to the server was when a url was bad (such as WebResource.axd), and then a request came back for that URL.