Why Clicking a hyperlink can result in multiple requests to web server(s)

re: Why Clicking a hyperlink can result in multiple requests to web server(s)

P.L. — Wed, 26 Apr 2006 17:57:55 GMT

Thanks for your detailed explanation. It is very clear to me, so far I know what happened on my web server.

HOWTO: Run Console Applications from IIS6 on Windows Server 2003, Part 2

David Wang — Fri, 28 Apr 2006 23:18:12 GMT

I finally have enough blog entries about various portions of IIS6 request processing that I can stitch...

re: Why Clicking a hyperlink can result in multiple requests to web server(s)

FrankT — Sun, 25 Nov 2007 23:16:48 GMT

My question is this: If you want to redirect to a logon URL inside of an ISAPI filter, and the the logon page itself that you are redirecting to has stylesheets, js file includes, etc... that cause the other http get's you mentioned above, how do you not get into an infinite loop? Because when my isapi filter sees the first request, it redirects to the logon page, but the logon url fetches images, stylesheets and some js files which once again executes the ISAPI filter and redirects to the url again...and again...and again.... Is there any variable in the server variables collection, etc...that can tell me what the other gets are related to an "original url" that was requested to avoid this infinite loop problem? I hope this makes sense...

Thanx in advance.