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.

re: 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.

Bertrand Le Roy — Mon, 15 Jun 2009 16:09:43 GMT

@Matt: yes, that issue is definitely real, and definitely different from this. The issue you're pointing to is still under active investigation by Dave Reed. I can get you in contact with him if you want details or if you want to help with the investigation. We have a number of hypotheses for this that we're looking at, one of which is browser cache corruption.

re: 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.

mattbrooks — Mon, 15 Jun 2009 10:15:42 GMT

@Bertrand: Please see this MS Connect issue for a similar but 'real' issue: connect.microsoft.com/.../ViewFeedback.aspx.

re: 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.

AndreiR23 — Wed, 10 Jun 2009 07:44:10 GMT

What I meant is if they (who reported the "bug") would have debugged using firebug or a similar tool they would have seen the request is served ok and wouldn't have reported the "bug" in the end.

re: 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.

Herman — Mon, 08 Jun 2009 07:11:27 GMT

@Bertrand: Yes, that's what he meant. Looking in Firebug would have already shown you nothing is wrong here, as the request returns a 200 status.

re: 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.

gunteman — Sun, 07 Jun 2009 22:06:27 GMT

The fact that the ampersands should be html encoded (and a lot of other things as well. HTML encoding is not used enough...) is something that should be shouted out loud to the web development community. I often encounter very experienced web developers that are completely oblivious to this fact, and often they even say "yeah, right".

re: 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.

Bertrand Le Roy — Sun, 07 Jun 2009 20:16:21 GMT

@Andrei: not sure what you're saying here: 200 is OK.

re: 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.

Andrei Rinea — Sat, 06 Jun 2009 08:52:31 GMT

Haven't thought it could be such a simple thing.. But still, if you would fire up firebug and watch the Net tab you would see a 200 code for the script request.