RE: HttpServletResponse.setStatus and setContentType (solved)

().close(); Hope that helps anyone else with a similar issue. Aaron Dunlop -Original Message- From: Dunlop, Aaron Sent: Wednesday, December 08, 2004 9:53 AM To: Tomcat Users List Subject: RE: HttpServletResponse.setStatus and setContentType Thanks for the suggestion, Yoav, but thus

RE: HttpServletResponse.setStatus and setContentType

sendError for errors, setStatus for normal responses. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Dunlop, Aaron [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 5:44 PM To: Tomcat Users List Subject: HttpServletResponse.setStatus and setContentType I have

HttpServletResponse.setStatus and setContentType

I have a standard HTTP servlet acting as an XML web service endpoint, running on an embedded Tomcat 5.0.30. I of course use HttpServletResponse.setContentType to specify that the response is text/xml. When the request is successful and I set a 2xx HTTP response code, the Content-Type header

Thread handling in Tomcat 4.x

Is there any scenario in which Tomcat 4.0 or 4.1 will kill off processor threads? I know that under apache, it is possible to limit the number of spare processes, in which case the controller process will kill off extras when load decreases. Alternatively, is there any error condition under

Cache-control on a per-application basis

which defaults to sending cache-control info restricting cacheing with each request. Thanks, Aaron Dunlop Aaron Dunlop Product Development Engineer DAT Services, TransCore Commercial Service Group [EMAIL PROTECTED]