On Tuesday 09 May 2006 20:34, Jonathan Vanasco wrote:
> On May 9, 2006, at 5:30 AM, Kjetil Kjernsmo wrote:
> > First of all, is it the intended behavior that libapreq2 should die
> > under these circumstances?
>
> yes.
>
> > If yes, are we supposed to deal with this by
> > putting each read of a co
The issue that i've come up with, is that some malformed cookies will
cause a segault when parsed. I'm hoping that the next libapreq will fix
that.
I remeber joes doing something about this. I'll have to go read it.
--
On May 9, 2006, at 5:30 AM, Kjetil Kjernsmo wrote:
First of all, is it the intended behavior that libapreq2 should die
under these circumstances?
yes.
If yes, are we supposed to deal with this by
putting each read of a cookie in an eval block?
yes.
Both are in the docs. I had no idea eith
Kjetil Kjernsmo wrote:
We have seen a problem with server errors when getting malformed
cookies. The problem has been seen before, we found from googling [1],
but it is not clear how we should address this. We are not quite
positive about the source of the malformed cookies, (it may have been
on
