My understanding is that with URL rewriting you can have a URL that looks like this:

http://url.com/page.aspx?param=value

and turn it into the following for the client to see:

http://url.com/the_most_amazing_page.aspx

I have tried the following in both the page load and application begin request events but nothing changes.

HttpContext context = HttpContext.Current; context.RewritePath("/test/test.aspx", false);

If I look at the value for context.Request.FilePath it is /test/test.aspx however the url has not changed. What am I doing wrong or what am I missing.

I think I've just realized that I haven't thought this through. It looks like the url rewriting is only visible on the server side and never rewrites the clients url. If I want the above to work the way I want I'd actaully need to add rewrite rules and urlmappings in the web.config.

By doing what I said programmatically just on pageload then the client would end up getting an 404 error when they tried to bookmark the page and go back to it.

I can't use the mappings as I am applying encryption that changes and could be different for the same information.

So basically I think I'm scrapping the idea of rewriting the url for the client.

the best solution i suggest is using ISAPI

Or may be you can use Global.asax

to enhance the question:

I do URL-rewrite in GlobalAsax, but it only works if the pages ends with aspx, so
..../test/bla.aspx works, but I would like to have it .../test/bla/.

This doesn't work since GlobalAsax is called only for identified .NET content. -> file doesn't exist message.

Does somebody has a solution workarround?

Originally Posted by rams0b

the best solution i suggest is using ISAPI

yeah, just use ISAPI and the problem is solved