Performance has tanked since going to https at remote locations

[WayneBeck]

After making the switch to SSL on our new 10.1 m040 system we have seen a very big performance decrease. An item that took 0:01:35 to add to workspace now is taking upwards of 14 min. Internally we are not seeing this except at our replication sites. Any idea where to look to get this decrease back? Some of these are on our WAN some are outside our firewall.

Thanks for your input..

[jessh]

Check httpd-ssl.conf in Apache's conf/extra directory.

Latest PTC Apache configuration has:

#BrowserMatch ".*MSIE.*" \
# nokeepalive ssl-unclean-shutdown \
# downgrade-1.0 force-response-1.0
# Adjust the default BrowserMatch to be a little more granular
# in downgrading connection features [PTC]
# All MSIE versions need ssl-unclean-shutdown
BrowserMatch "MSIE" ssl-unclean-shutdown
# MSIE versions 2-5 need additional downgrades
BrowserMatch "MSIE [2-5]" nokeepalive downgrade-1.0 force-response-1.0

whereas older versions had:

BrowserMatch ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0

(a long-time Apache default).

[jessh]

To clarify:

The newer configuration is the desirable one here, i.e. latest is greatest.