Home/ Questions/Q 130225
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T05:54:52+00:00

I am using Context.RewritePath() in ASP.NET 3.5 application running on IIS7. I am doing

  • 0

I am using Context.RewritePath() in ASP.NET 3.5 application running on IIS7.

I am doing it in application BeginRequest event and everything works file.

Requests for /sports are correctly rewritten to default.aspx?id=1, and so on.

The problem is that in my IIS log I see GET requests for /Default.aspx?id=1 and not for /sports.

This kind of code worked perfectly under IIS6.

Using Microsoft Rewrite module is not an option, due to some business logic which has to be implemented.

Thanks.

EDIT:

It seems my handler is too early in the pipeline, but if I move the logic to a later event, than the whole rewrite thing doesn’t work (it’s too late, StaticFileHandler picks up my request).

I googled and googled, asked around, can’t believe that nobody has this problem?

EDIT:

Yikes! Here’s what I found on the IIS forum:

‘This is because in integrated mode, IIS and asp.net share a common pipeline and the RewritePath is now seen by IIS, while in IIS6, it was not even seen by IIS – you can workaround this by using classic mode which would behave like IIS6.’

Final update: Please take a look at my answer below, I’ve updated it with results after more than a year in production environment.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. After some research, I’ve finally found a solution to the problem.

    I have replaced the calls to Context.RewritePath() method with the new (introduced in ASP.NET 3.5) Context.Server.TransferRequest() method.

    It seems obvious now, but not event Senior Dev Engineer on IIS Core team thought of that.

    I’ve tested it for session, authentication, postback, querystring, … issues and found none.

    Tommorow I’ll deploy the change to a very hight traffic site, and we’ll soon know how it actually works. 🙂

    I’ll be back with the update.

    The update: the solution is still not entirely on my production servers but it’s tested and it does work and as far as I can tell so far, it’s a solution to my problem. If I discover anything else in production, I will post an update.

    The final update: I have this solution in production for over a year and it has proven to be a good and stable solution without any problems.

    • 0