Question

Env: .NET 1.1

I got into this situation. Where I need to give a URL that someone could redirect them to our page. When they redirect they also need to tell us, what message I need to display on the page. Initially I thought of something like this.

• http://example.com/a.aspx?reason=100
• http://example.com/a.aspx?reason=101
• …
• http://example.com/a.aspx?reason=115

So when we get this url based on ‘reason’ we can display different message.

But the problem turns out to be that they can not send any query parameters at all. They want 15 difference URL’s since they can’t send query params. It doesn’t make any sense to me to created 15 pages just to display a message.

Any smart ideas,that have one URL and pass the ‘reason’ thru some means?

EDIT: Options I’m thinking based on Answers

Try HttpRequest.PathInfo

or Second option I was thinking was to have a httphanlder read

read the path like this – HttpContext.Request.Path

based on path act. Ofcourse I will have some 15 entries like this in web.config.

<add verb="*" path="reason1.ashx" type="WebApplication1.Class1, WebApplication1" />
<add verb="*" path="reason2.ashx" type="WebApplication1.Class1, WebApplication1" />

Does that look clean?

Answer 1

Thoughts:

• Path Info: http://msdn.microsoft.com/en-us/library/system.web.httprequest.pathinfo.aspx
  urls would be http://example.com/a.aspx/reason100, http://example.com/a.aspx/reason101, etc

• URL Rewriting : http://weblogs.asp.net/scottgu/archive/2007/02/26/tip-trick-url-rewriting-with-asp-net.aspx
  urls would be http://example.com/a/reason/100.aspx, http://example.com/a/reason/100.aspx, etc.

edit: both these approaches involve only one aspx page, but multiple urls pointing to it.