Now that Domino supports HTTP 1.1 I have a problem with IE when using HTTP 1.1. JavaScript in IE seems to behave differently when proeessing HTTP 1.1 responses versus HTTP 1.0 responses. This problem has been observed in many locations in my application. I am able to get the proper behaviour when I instruct IE not to use HTTP 1.1. However, this is not a practical solution to the end-user. So the questions I have are:
A) Can I tell the Domino HTTP server to support only HTTP 1.0?
B) Can I over-ride some pages to only respond with HTTP 1.0 headers?
C) Any other suggestions?
Thanks
Sam
Subject: Using HTTP 1.0 in R6
Out of curiosity, why would the version of the HTTP protocol affect JavaScript, especially since 5.0.x also supports HTTP 1.1? What specific JavaScript problemsa re you running into?
Cheers!
Luke
Subject: RE: Using HTTP 1.0 in R6
History.back() behaves differently, it does not keep user modified data on the previous screen. It seems to be related to the Cache.
Subject: That’s not it … Using HTTP 1.0 in R6
It isn’t really HTTP/1.1 v. /1.0. As you surmised, it is the cache settings. Domino 5 did not do that much with cache settings. 6 is smart enough to use newer cache settings, but dumb enough that it only uses those settings with HTTP/1.1 clients, which it assumes will support them, but not HTTP/1.0 clients.
Subject: RE: That’s not it … Using HTTP 1.0 in R6
Is that behavior changable with the good ol’ http.cnf?