DISQUS

ian holsman · 2 years ago

hey steve,
you should file a bug about it.

personally I can't verify it as I don't run windows. but in general the httpd project is more conservative than performance focused.

bwg · 1 year ago

This change fixed a problem we had after a patch update to apache resulted in IE clients not being able to access one of our enterprise Java apps over SSL through an ISA firewall.
The error seen in the ISA logs was:
Error Code: 500 Internal Server error. The context has expired and can no longer be used. (-2146893033)
By changing ssl.conf to only specify ssl-unclean-shutdown for MSIE 6+, the IE clients were able to use the application without errors.

Anonymous · 1 year ago

YEAHHHHHHHHH this is plain stupid and old age! Someone needs to look at this now!

Andreas Lange · 1 year ago

Sadly, it seems even IE7 can't do things properly - we'll have to keep going with nokeepalive even longer.

Here is a text tracking down AJAX issues in IE7 to keepalive: http://qfox.nl/notes?1

Scooter Hanson · 6 months ago

I'm glad to see you exclude nokeepalive. With a setup including an OCSP responder, that nokeepalive flag kills us with multiple pki cert validation requests per page load.

PatrickN · 2 weeks ago

I totally agree with you that the developers of the Apache Web server creates a great product despite of the fact that sometimes it makes some small mistakes like you mentioned. I hope that it would never happen again in the future. Well I have to find out if they have fixed this problem. Btw thanks for the interesting post!

Sincerely,

Craig Barteson from software application development