Forum Discussion
mahnsc
Nimbostratus
NimbostratusSelectively Disabling Keep-Alives
This is probably going to be another odd-ball post but there is a good reason for it.
We have a site with a recently discovered bug that sends our app servers into full garbage collec...
hoolio
Cirrostratus
CirrostratusDo you have any way to differentiate between the initial request and the second request? I suppose you could track POST requests by client IP and maybe user-agent plus the URI using the session table. You could remove the session table entry for that client if/when the response is received. If the client already has an unanswered request pending and sends another one from the same IP with the same user-agent to the same URI, you could send back a 503 or some other response. You would want to set a timeout when adding the session table entry to that the client would be able to make another request after the timeout expired.
Else, would extending the idle timeout on earlier requests help give the server more time to answer those requests and prevent the client from retrying it over and over again?
Aaron
