Re: URL refresh in passive mode

Scott Tully wrote:

>
>I learned allot more about how this works when i re-wrote the Authserver in JAVA.
>
>The answers: That's a good little buffer. It doesn't. Nothing.
>
>When the 204 is returned to the browser it will not make that request again.... The browser is actually not on the page with
>the 5 second meta refresh... it's in a limbo state. the request was made and the browser tried to retrieve a page from the
>gateway... so it went there and got told be the gateway "no content".... the meta refresh does not continue to refresh every
>five seconds because it's no longer part of the header information. it was lost when the request was made to the gateway.
>
>When the renew form is resubmitted every 450 seconds it resets the header which contains the meta refresh that sends the
>ticket to the gateway ASAP, or 5 seconds, to notify the gateway that the user is still there... so you really get 455 seconds
>between renews....
>
>  
>
Scott,
Thanks for the reply. It clears up a lot of things.

So the ticket gets refreshed every 450+5 seconds? What does the ticket 
really do? I compared the tickets over a few hours, and I see that the 
tickets are different indeed. What purpose does the ticket serve, if the 
popup is going to talk to the auth server every 450 seconds anyway?
--
Sameer