ansaurus

Question

Answer 1

+1 A:

The + symbol is also the symbol for a space when URL Encoded. Could it be your routes are set up expecting the plus, which never arrives because actually its a space? I'm not sure why this would work on your local machine, but not on the IIS box though.

Edit: An un-validated random page on the net suggests that certain symbols must be encoded unless being used for their specific purpose. I'm not sure this applies to the + as my thought is that it's special purpose is representing spaces in URLs - but I guess %20 is worth a shot if that helps in any way? (And I appreciate, + rocks for Friendly URLs way more than %20 does)

Amadiere 2009-10-12 18:57:08

Yeah I knew the + was for white space, route is setup to expect a string so I would assume this would be o.k.

Slee 2009-10-12 19:01:06

If you're expecting a space according to your route, then it's not this. Have you tried replacing the + with a %20, what result does that give?

Amadiere 2009-10-12 19:08:10

GAH - I want nice URL's so I guess I have to craft them myself. For some reason I assumed URLEncode would create valid URL's - how silly of me

Slee 2009-10-12 19:24:29

http://support.microsoft.com/kb/820129 - this is a registry setting that can be chnaged (AllowRestrictedChars) - not sure if I want to do this or not.

Slee 2009-10-12 19:30:27

Sucks. I think there is something missing with regards to the +. I don't suppose the error logs on IIS provided anything useful? Sometimes they can elude to other issues, but it'll probably be the fact that the + is in part of the "file" in the URL, rather than the QueryString? (speculation comment)

Amadiere 2009-10-12 19:31:13

ansaurus

tags:

views:

answers:

'+' causing bad request in URL's

related questions