After I commented the following lines in httpd.conf, the KeepAlive on a HTTPS server was working.
#BrowserMatch "Mozilla/2" nokeepalive #BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0 ...... #SetEnvIf User-Agent ".*MSIE.*" \ # nokeepalive ssl-unclean-shutdown # nokeepalive ssl-unclean-shutdown \ # downgrade-1.0 force-response-1.0 but I am not sure what is the negative impact of this disabling. If you know it, please let me know. Many Thanks, Q.Xie --- Joshua Slive <[EMAIL PROTECTED]> wrote: > On 10/14/06, Qingshan Xie <[EMAIL PROTECTED]> wrote: > > > > > KeepAlive (persistent-connections) and SSL can > work > > > fine together. > > > But many configurations (including the default) > > > include something like > > > BrowserMatch ".*MSIE.*" \ > > > nokeepalive ssl-unclean-shutdown \ > > > downgrade-1.0 force-response-1.0 > > > which turns them off for the majority of > browsers. > > > > Disabled the above line, but still did not see the > > keepAlive working in my HTTPS server. Any idea? > > It could be that you have keepalive turned off > elsewhere in your > config, or it could be that the clients are not > using http/1.1 or not > requesting keepalive connections. > > Joshua. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
