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 either a few months ago.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.
