Incorrect clock on client PC leading to immediate cookie expiry?<br><br><div><br><div class="gmail_quote">On 24 June 2010 13:42, James Spath <span dir="ltr"><<a href="mailto:jspath@pangeamedia.com">jspath@pangeamedia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Thu, Jun 24, 2010 at 5:30 AM, Paul Makepeace <<a href="mailto:paulm@paulm.com">paulm@paulm.com</a>> wrote:<br>
> I admit this is going to be epicly vague but... we've seen very<br>
> intermittent (every couple of weeks) reports of users not being able<br>
> to log in: they click login & are returned to the homepage<br>
> (symptomatic of no cookie/session). I finally caught one happening and<br>
> it seems Cat is creating a new session on each request. Unfortunately<br>
> our remote desktop app failed and I couldn't see what Firefox was<br>
> doing.<br>
><br>
> My next attack is to watch with LiveHTTPHeaders over the wire.<br>
><br>
> Any tips or suggestions on what this might be? Anyone else seen it?<br>
> Debug tips next time we catch it?<br>
<br>
Try <a href="http://www.charlesproxy.com/" target="_blank">http://www.charlesproxy.com/</a> instead ... it's worth the money (and<br>
even has a free trial).<br>
<br>
- Jim<br><br></blockquote></div></div>