Kbase P97958: The port opened by browser to the Webserver for WebSpeed is closed after each request
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/09/2005 |
|
Status: Unverified
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
IIS 5.0
IIS 5.1
IIS 6.0
SYMPTOM(s):
The port opened by browser to the Webserver for WebSpeed is closed after each request
The next request picks up a different TCP port and establish new TCP connections.
TCP keep-alive enabled on the browser
Both cgiip and wsisa.dll exhibit the same behavior
Both IIS 5 and IIS 6 exhibit the same behavior
Regular static HTML pages reuse the same port
The TCP streams between web server and web browsers are observed using a network sniffer
Need to keep persistent HTTP connection (reuse the same port)
CAUSE:
According to RFC 2616, persistent HTTP connections can be used only when the browser knows the length of the content sent back by the web server.
For static files, the web server can easily determine this, and send back a Content-Length header. However, for dynamic content (such as that generated by WebSpeed), there is no way for the web server to know the length of the content before streaming the content to the browser.
According to RFC 2616, if this happens, the only way for the browser to know when all the content has been received is when the connection terminates.
FIX:
None. Expected behavior. The problem could happen to all the dynamic pages even with non-WebSpeed application