strongarm_46960
Dec 12, 2008Nimbostratus
HTML apology based tcp timeout
Looking at the “oneconnect” tcp setting & “tcp settings in profiles”, I am having some difficulty in choosing which TCP timeout value would dictate when my iRule generated apology HTML (during all pool failure) page would be displayed at a specified timeout value.
I have to make sure that this HTML page will be displayed only if and after the client sends out the initial HTTP request to the website, and if 100 seconds elapses and no response page was received, then the apology page *must* be displayed to the user independent of the performance driven oneconnect properties.
Which tcp timeout value setting would control this requirement?
The criterion for delivering this apology page will not only be based on status code received from the backend, it should also be based on a timeout value of 100secs, for cases when no status code is sent but clients time is being expended.