Re: SSL and 408 error code (incomplete request)

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 increase the connect

Re: SSL and 408 error code (incomplete request)

- 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

SSL and 408 error code (incomplete request)

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

Session timeouts: ignore "periodic polling" URL?

Hi, We have a Servelts/JSP application Tomcat6. Our javascripts issues automatic, periodic polling requests (Ajax and Comet), in order to keep the view  up-to-date. Unfortunately this prevents sessions from timing out... Is there a way to tell Tomcat that some URL shouldn't affect session timeou

Re: Comet and multipart

Thanks :) You're correct about blocking inputStreams, but I actually need Tomcat to write a multipart *response*, on an OutputStream (the reading side is on the client, and our client-side programmers will manage it without blocking). I wondered whether I'll have to hand-code it (manually output

Re: Comet and multipart

on, 1/3/11, Filip Hanik - Dev Lists wrote: From: Filip Hanik - Dev Lists Subject: Re: Comet and multipart To: "Tomcat Users List" Date: Monday, January 3, 2011, 8:47 AM On 1/3/2011 7:48 AM, sol myr wrote: > Hi, > > We're implementing a CometServlet on top of Tomcat NIO conn

Comet and multipart

Hi, We're implementing a CometServlet on top of Tomcat NIO connector, using "long polling". Currently we're using the approach recommended by most tutorials: the client opens a connection and waits for a message (for a configured timeout); if such a message arrives, the client consumes it (e.g.

(Tomcat) Does NIO connector make a difference outside of 'Comet' ?

Hi, I've just started looking into the NIO Connector. And I see why it's great to combine NIO+Comet... But does it makes any difference outside of Comet? 1) Namely, if I only have old-fashioned Servlets (not a "CometProcessor") - will it improve performance to use NIO connector (versus the good

Re: [Tomcat] Can I see if 'maxThreads' is exceeded?

André and Mark - thanks very much for the quick replies. --- On Mon, 11/29/10, André Warnier wrote: From: André Warnier Subject: Re: [Tomcat] Can I see if 'maxThreads' is exceeded? To: "Tomcat Users List" Date: Monday, November 29, 2010, 6:21 AM Mark Thomas wrote: > O

Re: [Tomcat] Can I see if 'maxThreads' is exceeded?

Sorry, correction: on section 2, I meant to say "e.g. 30 on the above example" (wrote '50' by mistake). Thanks again. --- On Mon, 11/29/10, sol myr wrote: From: sol myr Subject: [Tomcat] Can I see if 'maxThreads' is exceeded? To: users@tomcat.apache.org Date: M

[Tomcat] Can I see if 'maxThreads' is exceeded?

Hi, I'm new to Tomcat management, and would appreciate help on the 'maxThreads' property of the Http Connector: 1) Please tell if I understood correctly: Suppose I configure 'maxThreads=100', and 130 users try to simultaneously access my Tomcat - then 100 users will be served immediately, and t

Re: [tomcat] : request.setCharacterEncoding ("UTF-8") doesn't work ?

Thank you very much, David Delbecq , for this detailed reply. David Delbecq <[EMAIL PROTECTED]> wrote: sol myr a écrit : >Hi, > > I'm having a problem with HttpServletRequest.setCharacterEncoding("UTF-8"). > Basically, tomcat seems to ignore it complet

[tomcat] : request.setCharacterEncoding ("UTF-8") doesn't work ?

Hi, I'm having a problem with HttpServletRequest.setCharacterEncoding("UTF-8"). Basically, tomcat seems to ignore it completely, and assume "latin1" encoding. Here's the details: - I have an html < form > where user should type data in *Chinese*. - The browser (IE6) knows

tomcat: can you control the encoding assumed by HttpServeltRequest.getParameter ?

Hi, I'm using tomcat 5.5.15. I have a servelt which reads parameters from a < form > , using HttpServletRequest.getParameter(). The catch is, parameters data (filled in by the user) is in Chinese. I noticed that even though my page encoding is "unicode", the browser (IE6) seems to se