Mark Thomas wrote:
Cookie handling is fundamentally a complete mess. Specifications exist
but are not fully implemented, are not consistent with related
specifications, etc.
Having tried to sort this out the last time around and having read
Jeremy's great work on documenting where we stand at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 2/4/14, 5:59 AM, André Warnier wrote:
Why is it exactly that we can come up with things like websockets
and HTML-5 and SOAP and java annotations, but not with a new
HTTP/HTML version which would make Unicode/UTF-8 the *default*, and
Chris,
a note :
Christopher Schultz wrote:
...
Without quoting, unquoted Cookie names and values may be any US-ASCII
character from 0x32 - 0x7e except for any of (( | ) | | |
@ | , | ; | : | \ | | / | [ | ] | ? | = | {
| } | SP | HT). None of the characters above are within that range,
André Warnier wrote:
Chris,
a note :
Christopher Schultz wrote:
...
Without quoting, unquoted Cookie names and values may be any US-ASCII
character from 0x32 - 0x7e except for any of (( | ) | | |
@ | , | ; | : | \ | | / | [ | ] | ? | = | {
| } | SP | HT). None of the characters above
On 03/02/2014 12:19, André Warnier wrote:
André Warnier wrote:
Christopher Schultz wrote:
Without quoting, unquoted Cookie names and values may be any US-ASCII
character from 0x32 - 0x7e except for any of (( | ) | | |
@ | , | ; | : | \ | | / | [ | ] | ? | = | {
| } | SP | HT). None of
2014-02-03 André Warnier a...@ice-sa.com:
André Warnier wrote:
Chris,
a note :
Christopher Schultz wrote:
...
Without quoting, unquoted Cookie names and values may be any US-ASCII
character from 0x32 - 0x7e except for any of (( | ) | | |
@ | , | ; | : | \ | | / | [ | ] | ? | = | {
Konstantin Kolinko wrote:
2014-02-03 André Warnier a...@ice-sa.com:
André Warnier wrote:
Chris,
a note :
Christopher Schultz wrote:
...
Without quoting, unquoted Cookie names and values may be any US-ASCII
character from 0x32 - 0x7e except for any of (( | ) | | |
@ | , | ; | : | \ | |
2014-02-04 André Warnier a...@ice-sa.com:
Konstantin Kolinko wrote:
2014-02-03 André Warnier a...@ice-sa.com:
André Warnier wrote:
Chris,
a note :
Christopher Schultz wrote:
...
Without quoting, unquoted Cookie names and values may be any US-ASCII
character from 0x32 - 0x7e except
Konstantin Kolinko wrote:
2014-02-04 André Warnier a...@ice-sa.com:
Konstantin Kolinko wrote:
2014-02-03 André Warnier a...@ice-sa.com:
André Warnier wrote:
Chris,
a note :
Christopher Schultz wrote:
...
Without quoting, unquoted Cookie names and values may be any US-ASCII
character
Cookie handling is fundamentally a complete mess. Specifications exist
but are not fully implemented, are not consistent with related
specifications, etc.
Having tried to sort this out the last time around and having read
Jeremy's great work on documenting where we stand at the present moment,
it
We have upgraded to Tomcat 7 from Tomcat 6 and we are now facing issues due to
some of the standard company cookies containing an é.
Tomcat 6 accepted the é but upgrading to Tomcat 7 we get an error if the é
is any parameter except for the 1st position. The error received is:
SEVERE: Error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kevin,
On 2/2/14, 2:31 PM, Callinswood,Kevin,VEVEY,GLOBE BTC wrote:
We have upgraded to Tomcat 7 from Tomcat 6 and we are now facing
issues due to some of the standard company cookies containing an
é.
Tomcat 6 accepted the é but upgrading to
We have a cookie generated by the home page of our intranet as follows:
Cookie:
GetUser_Properties=abc,abc,abc,abc,abc,abc,abc,abc,abc;
If you put an é in the first parameter e.g.
Cookie:
GetUser_Properties=abcé,abc,abc,abc,abc,abc,abc,abc,abc;
Then we get result = 200 (success)
If you
13 matches
Mail list logo