-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sol,
On 7/31/13 5:32 PM, sol myr wrote:
> Has anyone happened to stumble onto this issue, please: Our Ajax
> works perfectly as long as its non-secure. However, when switching
> to SSL we sometimes see 408 errors (incomplete request). This only
> ha
Thank very much, that sounds like a good property to tweak. we'll try it out :)
- Original Message -
From: Martin Gainty
To: Tomcat Users List
Cc:
Sent: Thursday, August 1, 2013 1:07 AM
Subject: RE: SSL and 408 error code (incomplete request)
what happens if you increas
- Original Message -
From: André Warnier
To: Tomcat Users List
Cc:
Sent: Thursday, August 1, 2013 1:56 AM
Subject: Re: SSL and 408 error code (incomplete request)
sol myr wrote:
> Hi,
>
>
> Has anyone happened to stumble onto this issue, please:
> Our Ajax works perfectly
sol myr wrote:
Hi,
Has anyone happened to stumble onto this issue, please:
Our Ajax works perfectly as long as its non-secure.
However, when switching to SSL we sometimes see 408 errors (incomplete
request). This only happens on ajax, and inconsistently (similar requests might
succeed on one
von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
> Date: Wed, 31 Jul 2013 14:32:39 -0700
> From: solmy...@yahoo.com
> Subject: SSL and 408 error code (incomplete request)
> To: users@tomcat.apache.org
>
> Hi,
>
>
> Has anyone happened to stumble ont
Hi,
Has anyone happened to stumble onto this issue, please:
Our Ajax works perfectly as long as its non-secure.
However, when switching to SSL we sometimes see 408 errors (incomplete
request). This only happens on ajax, and inconsistently (similar requests might
succeed on one moment, but fail
