RewritePath - Folder To a Query (How To?)

  • Thread starter Thread starter Tomasz J
  • Start date Start date
T

Tomasz J

Hello Developers,

I am trying to write a code inside BeginRequest event handler which would
rewrite the following path:
/myapp/user123
to:
/myapp/?user=user123
One requirement:
rewriting path *I do NOT want to specify any particular page*, and allow
ASP.Net to use the default one.
Click to expand...

Is it doable? No matter what I try I keep getting "resource not found".

Can it be accomplished with HttpContext.RewritePath? May be I should use
some other method instead?

Thank you for any pointers.

Tomasz J
 
Tomasz J said:
Hello Developers,

I am trying to write a code inside BeginRequest event handler which would
rewrite the following path:
/myapp/user123
to:
/myapp/?user=user123
Click to expand...

This is an important requirement because?
Is it doable?
Click to expand...

Possibly, but you've already implied that whatever the default document is
it should be script.
No matter what I try I keep getting "resource not found".
Click to expand...

IIS will not be inserting the various document names into the string for you
in this case.
Can it be accomplished with HttpContext.RewritePath?
Click to expand...

Only be manually determining what the file name should be, ugly.
May be I should use some other method instead?
Click to expand...

Yes assume default.aspx or some other fixed name.
 
Thanks for Anthony's input.

Hi Tomasz,

For ASP.NET runtime, it can not handle those requests that hasn't a
document extension(all the requestes should end with a document extension).
That's why you always get "resouce not found error". If you do need to
intercept all the requests(include the folder path requests), you may
consider using raw IIS ISAPI filter.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
I understand. After all it is for IIS to request the default page, not
ASP.Net

That leaves me with Response.Redirect(), but I just hate to impose this
additional round-trip.

Thank you.

Tomasz J
 
Back
Top