On Mon, Mar 2, 2015 at 6:20 PM, Rainer Jung rainer.j...@kippdata.de wrote:
Am 02.03.2015 um 13:34 schrieb Umesh Sehgal:
On Mon, Mar 2, 2015 at 5:25 PM, Umesh Sehgal umesh.seh...@gmail.com
wrote:
On Mon, Mar 2, 2015 at 3:52 PM, Rainer Jung rainer.j...@kippdata.de
wrote:
Am 02.03.2015
Am 03.03.2015 um 13:45 schrieb Umesh Sehgal:
On Mon, Mar 2, 2015 at 6:20 PM, Rainer Jung rainer.j...@kippdata.de wrote:
Am 02.03.2015 um 13:34 schrieb Umesh Sehgal:
On Mon, Mar 2, 2015 at 5:25 PM, Umesh Sehgal umesh.seh...@gmail.com
wrote:
On Mon, Mar 2, 2015 at 3:52 PM, Rainer Jung
Eric,
On 2.3.2015 23:45, Eric wrote:
I am trying to change the ciphers that my Tomcat 7 server supports. I am
using the APR connector. Here's the connector information in server.xml
with the line saying which ciphers to support:
Connector port=8443 executor=edgeExecutor
Hi,
One of the applications we are managing is using Jersey for its rest
interface.
This application initializes the rest service with tapestry, so we don't
want it to be initialized at startup by tomcat, and set the following
property in catalina.properties:
I am trying to use atmosphere for my web app running under tomcat 8.0.14, for
which I have to use async servlet and filters, In chrome I get error
*net::ERR_INCOMPLETE_CHUNKED_ENCODING * when call the async web resource ,
when I deploy this locally in the development machine I don't get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Fachhoch,
On 3/3/15 1:30 PM, fachhoch wrote:
I am trying to use atmosphere for my web app running under tomcat
8.0.14, for which I have to use async servlet and filters, In
chrome I get error *net::ERR_INCOMPLETE_CHUNKED_ENCODING * when
this is the link in staackoverflow
http://stackoverflow.com/questions/26863972/how-to-prevent-neterr-incomplete-chunked-encoding-when-using-html5-server-even
http://stackoverflow.com/questions/26863972/how-to-prevent-neterr-incomplete-chunked-encoding-when-using-html5-server-even
--
View
any update on the behavior of the patched nodes? Did it behave better,
ie.
did the problem reoccur on other nodes but not on the patched ones,
or were all nodes mostly without problems during the last 2 days? Any
strange things on the patched ones? I'd like to add the patch for
1.2.41
Hi,
I was wondering if there is an unintentional potential index of out bounds
exception in AbstractServletInputStream::readLine() ?
I was looking at the code in
java/org/apache/coyote/http11/upgrade/AbstractServletInputStream ,
specifically the readLine() function:
=
