Response.Redirect is done on the client side overall. The server sends an
"instant" redirect command and the client obeys. Can you capture the event?
There are a couple of ways, depending on your needs. One of the easiest is to
redirect with a command line variable (QueryString) and use that var to
realize it has been redirected. Another is to hang something in session that
a redirect happened. But, you cannot simply figure it out, as the server sees
the redirected hit just like any other hit to the site. As web servers are
stateless, you have to persist the fact a redirect was requested.

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
> Hi folks,
>
[quoted text clipped - 11 lines]
>
> -Eric
ewahl@nextmillenniumweb.com - 10 Jul 2006 18:39 GMT
That sounds like a way to handle redirects from the server side, but I
need to do something on the client side. If the server sends a
redirect, I want to be able to add some information to the querystring
before the redirect actually happens. But, this needs to happen on the
client side. (Assume that I have no control over what the server code
does, that I am simply fulfilling a requirement that I have for
client-side behavior.) Is there any way to do that? I realize this is
not standard behavior for a "regular" web browser, but I am trying to
emulate something that a third-party piece of hardware (that can web
browse) might do. Thanks.
-Eric
Cowboy - MVP (Gregory A. Beamer) wrote:
> Response.Redirect is done on the client side overall. The server sends an
> "instant" redirect command and the client obeys. Can you capture the event?
[quoted text clipped - 4 lines]
> the redirected hit just like any other hit to the site. As web servers are
> stateless, you have to persist the fact a redirect was requested.