You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by David Landis <dl...@gmail.com> on 2015/07/31 05:16:40 UTC
Tomcat 8.0.24 seems broken (empty POST body)
Just tried to upgrade my app from 8.0.20 to 8.0.24 and noticed I couldn't
login. The POST requests were correct on the client side but had an empty
body on the server side.
So instead I tried upgrading to 8.0.23 and everything works perfectly fine
there. Looked at the 8.0.24 changelog and didn't see anything obvious.
Env:
CentOS 7
apr connector
java 8
Example headers:
POST /app/Login HTTP/1.1
Host: localhost:8443
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101
Firefox/31.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-Requested-With: XMLHttpRequest
Referer: https://localhost:8443/app/
Content-Length: 35
Cookie: JSESSIONID=jaksjdfkjasdkljflkajsdf
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
Re: Tomcat 8.0.24 seems broken (empty POST body)
Posted by David Landis <dl...@gmail.com>.
On Fri, Jul 31, 2015 at 8:19 AM, Christopher Schultz <
chris@christopherschultz.net> wrote:
>
>
> To be fair, it would be easy to read the first phrase in that
> changelog entry and conclude "I'm not using multipart/form-data" and
> ignore the rest of the entry.
Indeed, I think that's how most people would read it. Even reading the
whole paragraph it seems like the second sentence is referring to
multipart, when actually it is just a completely different change.
And anyway, shouldn't changing the meaning of public config parameter in a
breaking way at least warrant a minor release instead of a point release?
Re: Tomcat 8.0.24 seems broken (empty POST body)
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Mark,
On 7/31/15 2:20 AM, Mark Thomas wrote:
> On 31/07/2015 04:16, David Landis wrote:
>> Just tried to upgrade my app from 8.0.20 to 8.0.24 and noticed I
>> couldn't login. The POST requests were correct on the client side
>> but had an empty body on the server side.
>>
>> So instead I tried upgrading to 8.0.23 and everything works
>> perfectly fine there. Looked at the 8.0.24 changelog and didn't
>> see anything obvious.
>
> Really? Look again at the first entry in the changelog for 8.0.24.
To be fair, it would be easy to read the first phrase in that
changelog entry and conclude "I'm not using multipart/form-data" and
ignore the rest of the entry.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVu5HrAAoJEBzwKT+lPKRYa54QAJj0NmcpQJy85F8qhQN1wy68
xwXYd7OzMTBvnhBfyXXVnLIqP29KxMRRUgmIo6xH98urSd71q/mVW89LrXlo/lYa
5y7c96r65UQ+Cm0MDti8vVjzILkhA5iGcomBvzU444lA8IiSNT4xUzJX8pmPgtBn
iMtlgQYk7ExJ6vLGhzcHY0A1CRGCmdLqNNFrKFgxTmF/Dy5jK9ZMMZhWpsUnr/LW
z4L72CCY6yUalYnSKWoQwhEKfrPpZ6Z9/K4/vZvpJGUGwUf1XAdd9s8/Ki40ORjQ
tAgWKqybuQssH6Qda3W3v+9vLhUuFdxQRdEmG67LLmQc3LkEYfAPq3WalLSyXV3i
0cuXyFStoc3Ag61hNbpnkRBiKOVWp4ffeRv3TM5ICT+z2Kwe5sEx7X0jF8YM+Q6j
SpDt0vg39U2tKT3122022KhyC6GkkE20UUY4GLbyfnDZqSTAd7WWQXrmACrBZrQu
epGs6MD6hdzmP00cks5MLlk1FF9Au8JcTz60e5XHFPd1NwE462SOvjKtm6D2pGQk
5ArhW55eM7tauuZutllK5G45tc7/+gVBO+27X01GlBt9/9kaxX9Dj5EXssfzIGK7
Uyq1DefltOfrl4I6J+tQUubUMPmCc23qIw7q91buaZEoQixrfzMIaXO+QIYpethA
PAwfwSSZwpjt8BRT7PUa
=OiIC
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 8.0.24 seems broken (empty POST body)
Posted by Mark Thomas <ma...@apache.org>.
On 31/07/2015 04:16, David Landis wrote:
> Just tried to upgrade my app from 8.0.20 to 8.0.24 and noticed I couldn't
> login. The POST requests were correct on the client side but had an empty
> body on the server side.
>
> So instead I tried upgrading to 8.0.23 and everything works perfectly fine
> there. Looked at the 8.0.24 changelog and didn't see anything obvious.
Really? Look again at the first entry in the changelog for 8.0.24.
Mark
>
> Env:
> CentOS 7
> apr connector
> java 8
>
>
> Example headers:
>
> POST /app/Login HTTP/1.1
> Host: localhost:8443
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101
> Firefox/31.0
> Accept: */*
> Accept-Language: en-US,en;q=0.5
> Accept-Encoding: gzip, deflate
> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
> X-Requested-With: XMLHttpRequest
> Referer: https://localhost:8443/app/
> Content-Length: 35
> Cookie: JSESSIONID=jaksjdfkjasdkljflkajsdf
> Connection: keep-alive
> Pragma: no-cache
> Cache-Control: no-cache
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org