On Tue, 19 Sep 2006, Derek R. Price wrote:
Philip M. Gollucci wrote:
http://svn.apache.org/viewvc?view=revrev=447770
How's that ?
Looks good to me. Dave?
Not as good as actually _being_ backwards compatible, but if it's
documented I can't complain.
-dave
Derek R. Price wrote:
Now, using the same Perl source with Apache2::Cookie-new, an undefined
value is returned instead of the new cookie. At best, this appears to
be an API change and should be documented. At worst it appears to be a
bug in libapreq2 that should be fixed.
Hello,
If this isn't the correct place to report this problem, please excuse
the noise and redirect me...
Apache::Cookie-new used to deal gracefully with an undefined -value
argument (like: ...new (-name = 'some_cookie', -value = undef,
...)), at least when -expire was in the past (-1D in my
This same problem occurs if I call A2::C-new without any value argument
(...new (-name = 'some_cookie', -expire = '-1D', -path = ...,
-secure = 0)), though I didn't verify the A:C-new behavior with no
-value at all (only with -value = undef...).
Derek
Derek R. Price wrote:
Hello,
If this
