Search results matching tag 'url encoding'

Replacing characters in URL

michaelabruce — Tue, 03 Nov 2009 14:41:02 GMT

I want to replace all instances of an embeded space %20 with an underscore. I don't see anything here that would allow a URL with encoded spaces such as http://localhost/folder/this%20is%20my%file.aspx to http://localhost/folder/this-is-my-file

Any ideas?
Thanks,
Michael

Re: Url Rewrite when there are spaces

ruslany — Wed, 17 Dec 2008 18:26:53 GMT

The original rule that you have should work here. When you say that rule does not work - does it mean that it is not executed or it results in error?

Re: Problems with URL_Rewrite Mediawiki

ruslany — Tue, 02 Dec 2008 17:58:06 GMT

Try using the urlencode function:

Re: Rewrite decodes and changes original url in X_ORIGINAL_URL

ruslany — Mon, 03 Nov 2008 17:52:43 GMT

In the upcoming RTW release, URL rewriter will set another IIS server variable - UNENCODED_URL - to contain the raw URL exactly as it was requested by the browser (all encoding preserved).

HTTP_X_ORIGINAL_URL will still contain decoded URL.

Re: Rewrite decodes and changes original url in X_ORIGINAL_URL

ruslany — Wed, 29 Oct 2008 04:38:56 GMT

Ok. I think this is clear to me know. This looks like a common approach used by PHP apps, where everything is rewritten to index.php and then the app figures out what to do based on original url.

I'll let you know what we'll decide on this.

Re: Rewrite decodes and changes original url in X_ORIGINAL_URL

ruslany — Tue, 28 Oct 2008 23:54:06 GMT

Do you need to use original encoded URL to construct the links in your web application only? Or do your rewrite rules rely on the URL being encoded when doing pattern matching?

Re: Rewrite decodes and changes original url in X_ORIGINAL_URL

ruslany — Tue, 28 Oct 2008 19:17:19 GMT

The fix for non-ascii characters will not change this behavior.

IIS gets already decoded URL from https.sys and that is used to set HTTP_X_ORIGINAL_URL as well as any other server variables. This is not specific to URL rewriter and this is how it is in IIS 6.

Could you explain why it is a problem for your client?