lighty labs

2008-11-20

19:06 Lighttpd Support: RE: Partial Cookies being written or read (FastCGI)

Sorry - I am not able to reproduce the problem in testing - though it still exists in production - I wish I could. I... eudlawil

2008-10-28

18:38 Lighttpd Support: RE: Partial Cookies being written or read (FastCGI)

That is definitely a possibility - but I'm doubtful that this is the case.
It certainly is the easiest explanation... eudlawil

2008-10-27

17:51 Lighttpd Support: RE: Partial Cookies being written or read (FastCGI)

So... the upgrade of Perl's CGI (CGI::Fast) didn't help.
After many days of collecting data I find that MSIE neve... eudlawil

2008-10-24

20:21 Lighttpd Support: RE: Partial Cookies being written or read (FastCGI)

Oh, hey... here's a curious example of bad cookie data that may provide a clue...
936:1:63346362176:1:68:68:263:63... eudlawil

20:13 Lighttpd Support: RE: Partial Cookies being written or read (FastCGI)

I'd love to... but I can't recreate the problem. It only happens occasionally. As I said we have about 1.5 million ... eudlawil

17:31 Lighttpd Support: RE: Partial Cookies being written or read (FastCGI)

One additional note:
I'm now capturing the browser agent where these messed up cookies reside - and it appears to ... eudlawil

2008-10-22

19:27 Lighttpd Support: Partial Cookies being written or read (FastCGI)

* Issue:
We write at least two, and sometimes three cookies to a user's browser for
each request we get. W... eudlawil

2008-10-17

18:21 Lighttpd Support: RE: After upgrade non-fastcgi scripts don't log to error.log

Thanks for the explanation - I guess I was so used to the way apache the the older version of lighty handled this.
... eudlawil

2008-10-15

19:34 Lighttpd Support: RE: After upgrade non-fastcgi scripts don't log to error.log

Thanks, stbuehler, for the quick reply!
However, I have to say that I don't understand it.
First off, why did thi... eudlawil

2008-10-14

22:17 Lighttpd Support: RE: After upgrade non-fastcgi scripts don't log to error.log

Me again...
Some additional info:
* I back rev'd to 1.4.19 and this issue disappears.
* After upgrading to 1.... eudlawil