Parse URL From 404 In ASP/IIS So That I May Query DB For Possibles

I did that, I think missed the part where I wrote originally:

 " I tried using Request.ServerVariables("URL") for capture the folder like normal, BUT it returns the 404.asp page instead of '/john/' "

IIS returns the page you assigned it for the 404, it doesn't return what the URL shows.

Any solution?  Anyone?

Ben

>>>
try
Request.ServerVariables("HTTP_Referrer")
<<<

>>>
Was this comment helpful? Yes No
I did that, I think missed the part where I wrote originally:

 " I tried using Request.ServerVariables("URL") for capture the folder like normal, BUT it returns the 404.asp page instead of '/john/' "

IIS returns the page you assigned it for the 404, it doesn't return what the URL shows.

Any solution?  Anyone?

Ben
<<<

The "URL" server variable returns the current page URL without querystring or path.  The "HTTP_Referrer" variable returns the URL of the page that links to the current page.  They are *not* the same thing.  Please give ArachnidCreations the points.

Ok... let's try this one more time.... PLEASE READ what I originally wrote.  It's CLEAR as day, yet it appears that nobody is reading what I write.

Request.ServerVariables("URL") will NOT work because it returns the value  '404.asp' instead of what's in the URL, like the example /john/

In IIS, I have it using 404.asp for 404 errors, although 404.asp does not show in the URL when you type in a folder /john/ which does not exists, Request.ServerVariables("URL") will return the value '404.asp' STILL.

Looking forward to your thoughts.  Thanks.

Ben

Look at Request.ServerVariables("query_string").

http://forums.iis.net/t/1158734.aspx

For the matter, run through the Request.ServerVariables collection to enumerate all the values.  You may find other interesting bits of information in there.

In the end, you may have to face the simple fact that IIS mangles request data as it passes control to custom error pages.  I first encountered similar issues when I was trying to port my own cart software from LAMP to WIMP (what an appropriate acronym..hrrmm).  The same code with the same PHP/MySQL versions failed because IIS does not populate the subsequent error page request in quite the same way as the original request.  Due to other workloads, I was unable to delve into the problem as thoroughly as I would have liked, but I recall that the information I needed (POST, for example) simply did not exist in the request information passed to PHP.