Re: White-space encoding issue in 8.5.16

2017-11-13 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

To whom it may concern,

On 11/13/17 4:10 AM, M. Manna wrote:
> Actually, it's the same issue (and even error stack) reported
> here:
> 
> http://tomcat.10.x6.nabble.com/Tomcat-8-5-4-uses-RFC-6265-by-default-w
hich-does-not-appear-to-be-Servlet-3-1-compliant-td5054685.html

So
> 
you are having an issue with cookie values?

Are you expecting the cookie values containing spaces to be converted
to %20 while writing responses or are you finding that cookie values
containing spaces aren't being converted to %20 for you when reading
requests?

I wouldn't expect the container to perform either of those actions.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAloJuv8dHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFibxhAAvymYP9xusV8I0OvV
GKk2QnTWpnJTNU+fJkmXacmltb1ZUCPBdw1H+W1u1n6L+adQnGmgoLbpSRZ2cWzk
52lnlypV+SqfVCgw32tTpXOV0oJwlPc7HmftRyilmjmiGuIkY1XupHGiJ3ShtIDi
zTrIoCqtgJ1MFoITBKTtN6Z7P4t41p9sDCSPatVonmPsOWFqAlTXLUXfEMhQX0XZ
wIXGIk1mUu02477vHA+5JFPwhzJNsla12PBlHhq3dLHSHJjG99T2wRqkNrJYTRWU
0JE8/n02XAfnCwMn1UNpK7SYArp2j5JFgvOmHmc7mT8HrL8cUOgxy/fjKIstyz9c
GBKMIbu9glLG+iOKbQ94mkw8cxx/X55tvlbG+MkjockfQn6ys7vUwtUN/4ZvIGiS
ToudjhZbG60UJ/ImHEvf/hD2A+FJPpO9ko9oxHKRS3XKK+G3R9ZreJCDQBSXyvgX
QyOIE8RB/8RMyaQFiVPtSi13Rp+dheIdglArRjxPCygHlbJXIShpd+Nse5/zvfd7
ikeIZCrf+PCDw5g8jCcl58thfjgL/ffmuUCrtig8/VQ4clRE3SxHGebuouQYv53T
eva07X6jOwBqJw8GbYIZl3mT3iM6F2WBaErQy0YU+q6r2bCrhoUZjvVLP+HMWtsF
HEHsllOy5nlxKDRA0DeZwWjXSSs=
=VWgo
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: White-space encoding issue in 8.5.16

2017-11-13 Thread M. Manna
Actually, it's the same issue (and even error stack) reported here:

http://tomcat.10.x6.nabble.com/Tomcat-8-5-4-uses-RFC-6265-by-default-which-does-not-appear-to-be-Servlet-3-1-compliant-td5054685.html



On 13 November 2017 at 09:00, Mark Thomas  wrote:

> On 12/11/17 22:25, M. Manna wrote:
> > Hi,
> >
> > We are currently encountering an issue where some of our REST  API calls
> > are failing because of a white-space not being encoded (i.e. %20). This
> has
> > started with 8.5.16 and our previous version didn't have this problem -
> > 8.0.29.
> >
> > Is this something anyone has seen before? I am assuming that it's RFC
> 6265
> > where whitespace is not allowed? But is there any work around?
>
> You are going to need to be more specific about the problem. You need to
> provide enough information for someone else to reproduce the issue and
> investigate it.
>
> Mark
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


Re: White-space encoding issue in 8.5.16

2017-11-13 Thread Mark Thomas
On 12/11/17 22:25, M. Manna wrote:
> Hi,
> 
> We are currently encountering an issue where some of our REST  API calls
> are failing because of a white-space not being encoded (i.e. %20). This has
> started with 8.5.16 and our previous version didn't have this problem -
> 8.0.29.
> 
> Is this something anyone has seen before? I am assuming that it's RFC 6265
> where whitespace is not allowed? But is there any work around?

You are going to need to be more specific about the problem. You need to
provide enough information for someone else to reproduce the issue and
investigate it.

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



White-space encoding issue in 8.5.16

2017-11-12 Thread M. Manna
Hi,

We are currently encountering an issue where some of our REST  API calls
are failing because of a white-space not being encoded (i.e. %20). This has
started with 8.5.16 and our previous version didn't have this problem -
8.0.29.

Is this something anyone has seen before? I am assuming that it's RFC 6265
where whitespace is not allowed? But is there any work around?

Kindest Regards,