antic
Perch
Hi all,
Just wondering if anyone's had any experience doing this. I have set up an error page to handle 404's, which checks the URL and under certain circumstances returns a file or a page to the browser.
Example: www.domain.com/thispath/thatfile.pdf - does not exist, but it matches a set of valid calls, so the 404 script returns the relevant PDF file to the browser. The 404 script is called "catchthis.asp".
However, in the IIS log (and therefore Webalizer/AWStats), instead of seeing hits recorded for "/thispath/thatfile.pdf", all the hits are being recorded for "/catchthis.asp" (with a special 404 querystring that IIS puts on the end).
Soooo the $63999.95 question is, how can I get IIS to record the "real" URL in the log (and in webalizer etc.)? Anyone managed to do this in the past?
Just wondering if anyone's had any experience doing this. I have set up an error page to handle 404's, which checks the URL and under certain circumstances returns a file or a page to the browser.
Example: www.domain.com/thispath/thatfile.pdf - does not exist, but it matches a set of valid calls, so the 404 script returns the relevant PDF file to the browser. The 404 script is called "catchthis.asp".
However, in the IIS log (and therefore Webalizer/AWStats), instead of seeing hits recorded for "/thispath/thatfile.pdf", all the hits are being recorded for "/catchthis.asp" (with a special 404 querystring that IIS puts on the end).
Soooo the $63999.95 question is, how can I get IIS to record the "real" URL in the log (and in webalizer etc.)? Anyone managed to do this in the past?