Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 21 Dec 2010 17:09:28 -0800 (PST)
From: Mark Hedges <hedges@formdata.biz>
To: Joe Schaefer <joe_schaefer@yahoo.com>
cc: apreq-dev@httpd.apache.org
Subject: Re: skip bad cookie value in Apache2::Cookie::Jar?
In-Reply-To: <994077.51308.qm@web54403.mail.re2.yahoo.com>
Message-ID: <alpine.DEB.2.00.1012211708160.24857@maggie.scriptdolphin.com>
References: <alpine.DEB.2.00.1012211518540.24857@maggie.scriptdolphin.com>
 <994077.51308.qm@web54403.mail.re2.yahoo.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 21 Dec 2010, Joe Schaefer wrote:
> > Could Apache2::Cookie::Jar maybe have an option to skip
> > NOTOKEN  errors when reading the jar?  Then it would do
> > something like  below.  Or does the eval have to happen in
> > the 'each %attrs' loop of  Jar->new().
>
> The issue has nothing to do with browsers.  It has to do
> with 3rd party apps that generate bogus cookies. If you
> want apreq to ignore those cookies, just use eval {} and
> trap the exception.
>
> If you want to fix those 3rd party cookie apps, it's good
> that apreq lets you know there's a problem.
>

That makes sense.  Now I get the jar with eval { } in my
thing only if a directive is set to do that.  Thanks for
the input.

--mark--