Why is ASP.NET encoding &s in script URLs? A tale of looking at entirely the wrong place for a cause to a non-existing bug.
Posted by: More Whidbey stuff,
on 06 Jun 2009 |
View original | Bookmarked: 0 time(s)
Several people have reported seeing errors in their logs that seem to be due to requests such as this: /ScriptResource.axd?d= [lots of junk]& t=ffffffffee24147c The important part here is the HTML-encoded & sequence, which stands for & of course. If this exact URL is sent to the server, the server wont know what to do with the escape sequence (URLs are not supposed to be HTML-encoded on the wire) so the parameters wont get separated as expected, potentially resulting in a server...