On 21-Apr-2009, at 10:15, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre-John,
On 4/16/2009 5:48 PM, Andre-John Mas wrote:
Will this only be for writing? I depend a cookie set by a third-party
web application in the same domain, which sends me the cookies this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre-John,
On 4/16/2009 5:48 PM, Andre-John Mas wrote:
> Will this only be for writing? I depend a cookie set by a third-party
> web application in the same domain, which sends me the cookies this
> way. If it is only for writing, then I will have to
Andre-John Mas wrote:
>
> On 16-Apr-2009, at 17:08, Mark Thomas wrote:
>
>> Using a ':' in a v0 cookie is not legal. You have to use a v1 cookie
>> which is as simple as using:
>> cookie.setVersion(1);
>>
>> 5.5.28 will (hopefully - if it gets enough votes) an feature (enabled by
>> default) to a
On 16-Apr-2009, at 17:08, Mark Thomas wrote:
Using a ':' in a v0 cookie is not legal. You have to use a v1 cookie
which is as simple as using:
cookie.setVersion(1);
5.5.28 will (hopefully - if it gets enough votes) an feature
(enabled by
default) to automatically switch invalid v0 cookies t
Andre-John Mas wrote:
> Hi,
>
> The company I am working for is in the process of migrating from Tomcat
> 5.x.x to Tomcat5.5.27. In doing so we noticed that the any cookie value
> containing a colon will have the value trimmed up to before that
> character. This is new. A work around is to add quo
Hi,
The company I am working for is in the process of migrating from
Tomcat 5.x.x to Tomcat5.5.27. In doing so we noticed that the any
cookie value containing a colon will have the value trimmed up to
before that character. This is new. A work around is to add quotes
around the value, but
