It's not a secret anymore!*
The moose likes JSP and the fly likes Keep Alive and Dynmic Pages (JSP or Servlets) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » JSP
Bookmark "Keep Alive and Dynmic Pages (JSP or Servlets)" Watch "Keep Alive and Dynmic Pages (JSP or Servlets)" New topic

Keep Alive and Dynmic Pages (JSP or Servlets)

Deena Yousef

Joined: Dec 30, 2002
Posts: 1
During my tests on JRun I encountered the following interesting scenario, when I enabled the Keep Alive on the Server and Browser, and tried to open the main page on a copy of my app hosted on Jrun, the browser keep asking for the page, as if the download never stops, till the browser timeout after a while.

I was reading about such cases, and found the following:

- Keep alive will generally be used by JWS only if the following conditions are true:
- The browser asked for it with a "Connection: Keep-alive" header
- The servlet set the "Content-length" header prior to flushing any output
- The servlet did not set the "Connection: close" header

can anyone give me any examlples on how to use apply these points?
Please this is important, and thanks for anyone that can help..
jQuery in Action, 2nd edition
subject: Keep Alive and Dynmic Pages (JSP or Servlets)
Similar Threads
how to find out the page the user was previously at.
How to Close the Response Object at ServerSide?
keep connection
redirecting servlet fails with embedded jsessionId
Why null is return?