After 60 secs of inactivity, the proxy server has ended all connections with the client and server.
The client acknowledges knows these connections have ended. The client sends a POST to the website, however IIS/Sitecore replies ‘Invalid method 405’.
Ie) you are not allowed to send a ‘POST’ right now... we’re expecting another GET. When the proxy is not involved the connections between client and server stay open...
ie) the webserver is not sending the HTTP FIN ACKs that the proxy server does to clean up the client connections. The client correctly assumes the connection is still open and continues with ‘GET’ messages... the server happily responds.
I’m not sure if the webserver is closing the connections when the proxy server requests. For whatever reason, it is still having the connection open when the client tries to begin a new conversation. The proxy attempts to close client and server connections at the same time (after 60 secs idle). The client responds... i can’t say the same for the server. The client tries to begin a new conversation and the server is not ready.
- Is the SiteCore app proxy aware?
- Why does it fail to respond to a new POST? If the proxy has sent a HTTP FIN ACK to client and server after 60 secs idle.
How do we solve this?
a. SSL?
b. IIS setting?
c. Increase idle timeout on proxy? Not ideal... we have too many connections.
The proxy server is Websense/Surfcontrol and it is HTTP RFC Compliant. I have increased the idle timeout from 1 to 10 mins since the problem was discovered last week.
It has not helped and we see Invalid Method after 60 secs of inactivity. We are not cutting of incomplete transactions; we are only ending sessions that facilitated a completed HTTP transaction where the 200 server response had been received at client.
I have seen other questions regarding http error 405, but none seems to fit my case. Is something wrong with with Sitecore or is it as usual Microsoft bugs?
Sitecore version: 6.2 IIS version: 6