Chris - The header logging is a good idea. We'll add that. In the meantime,
it looks like it might have been premature to indicate that "the problem
persists with HTTP/1.1". The one instance that I found was a red herring,
so to date the problem has *not* recurred since addressing the HTTP/1.0
issu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chad,
On 2/27/18 9:02 PM, Chad Stansbury wrote:
> Thanks for your response. Unfortunately it doesn't appear to be a
> bad cookie name or value, as the identical set of cookies are
> passed (and parsed correctly) on requests that immediately precede
Hello Chris -
Thanks for your response. Unfortunately it doesn't appear to be a bad
cookie name or value, as the identical set of cookies are passed (and
parsed correctly) on requests that immediately precede and follow the
failing request. That's pretty clear from both the Wireshark and Tomcat
ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chad,
On 2/27/18 9:44 AM, Chad Stansbury wrote:
> We've been troubleshooting an issue where our web application is
> getting a very occasional request that contains no cookies even
> though a Wireshark on the application server shows those cookies
>
We've been troubleshooting an issue where our web application is getting a
very occasional request that contains no cookies even though a Wireshark on
the application server shows those cookies coming in on the request.
I was able to replay the request that was captured via Wireshark, and when
doi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego,
On 1/19/2011 12:08 PM, Diego Monni wrote:
> MessageContext inMsgCtx1 =
> stub1._getServiceClient().getLastOperationContext().getMessageContexts().get("Out");
> String incomingCookie1 =
> (String)inMsgCtx.getServiceContext().getProperty(HTTPCons
I use whireshark in order to snif the transaction because de the proxy class
return null
MessageContext inMsgCtx1 =
stub1._getServiceClient().getLastOperationContext().getMessageContexts().get("Out");
String incomingCookie1 =
(String)inMsgCtx.getServiceContext().getProperty(HTTPConstants.COOKIE_ST
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego,
On 1/19/2011 9:48 AM, Diego Monni wrote:
> Thanks for the response.
> I mean that my application contains jsp pages and webservices. When I call a
> jsp page the jsessionid is present. When I invoke a service method in the
> response header jse
Thanks for the response.
I mean that my application contains jsp pages and webservices. When I call a
jsp page the jsessionid is present. When I invoke a service method in the
response header jsessionid is not present.
diego
2011/1/19 Caldarale, Charles R
> > From: Diego Monni [mailto:diego.mo.
> From: Diego Monni [mailto:diego.mo...@gmail.com]
> Subject: cookies and webservice
> I have to use a webservice (tomcat 7.0.0. + axis2 1.5 + jdk 6.0.21)
Try it again on a stable version of Tomcat (7.0.6).
> but in the response there isn't the jsessionid. In the application context
> the flag
gt; Thank you for the response
>
> JLM
>
>
>
>
>> Message du 19/06/09 13:53
>> De : "Mark Thomas"
>> A : "Tomcat Users List"
>> Copie à :
>> Objet : Re: Cookies handling issue
>>
>>
>> mateo-jl wrote:
>>&
19/06/09 13:53
> De : "Mark Thomas"
> A : "Tomcat Users List"
> Copie à :
> Objet : Re: Cookies handling issue
>
>
> mateo-jl wrote:
> > Hi everybody,
> >
> > recently i've reported a problem, which wasn't a new one, related
mateo-jl wrote:
> Hi everybody,
>
> recently i've reported a problem, which wasn't a new one, related to the
> encoding base64 within cookies ("=" separator ... only at reading :
> request.getCookies) .
> I was responded that this problem will probably be corrected with Tomcat
> 6.0.19 or 6.0.
Hi,
This issue probably won't be given a great deal of attention. There's conflict
between what the spec says, and what has actually been going on in the
development world. The de facto reality is that people have been using =
characters in cookies despite them being prohibited for a long time.
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
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Cookies
>
> So is it the case that if browser B has previously set a
> cookie at site S (at url uuu), then when B returns to uuu
> (say after many days but before the cookie for uuu has
> expired), B sends the cookies for uuu in the /first/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken,
Ken Bowen wrote:
> So is it the case that if browser B has
> previously set a cookie at site S (at url uuu), then when B returns to uuu
> (say after many days but before the cookie for uuu has expired), B sends
> the cookies for uuu in the /first
e fixed
already.
I am going to try that live http headers.
-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Monday, August 6, 2007 05:01 PM
To: 'Tomcat Users List'
Subject: Re: cookies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony,
[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony,
[EMAIL PROTECTED] wrote:
> I just did a responses to this and somehow it got lost ;-(
I hate it when that happens. :(
> Cookie oreo;
Very clever ;)
That code looks fine, by the way. The fact that cookies.length is 1
probably means that the
de", err.errcode);
c.put("errormsg", err.errmsg);
tmpl.write(out, c);
out.flush();
}
-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Monday, August 6, 2007 01:55 PM
To: 'Tomcat Users List'
Subject: Re: cookies
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony,
[EMAIL PROTECTED] wrote:
> He has something called login.html which uses a login.java compiled
> program to set a cookie (response.addCookie( "UserLevel", "value") )
> which adds a cookie called UserLevel with a value retrieved from
> logging in
25 matches
Mail list logo
