Back button is SUPPOSED to retrieve the page from local cache. If cache is not available for any number of reasons, the page will be reloaded and you will lose your input. Simple fix MOST of the time is to clear temp files. Some browsers may have a separate "clear the cache" option. Some web sites, particularly order entry, go to great lengths to disable your back button from going to cache, but that is not the case here. HTTP is a stateless protocol, that is, no permanent connection is made with the host. Your request makes a connection, the server gets the request, does it's thing, sends a response, and then CLOSES the connection. Your browser has made the request, is reading the connection and is waiting for the connection to be closed. Once the yt host has posted the message, sent your response, and closed the socket, there are quite a few players in the loop getting that all back to you. TCP/IP is very tolerant in waiting for that close socket message. All that said, given the very high occurance of losing the close socket (based on the level of douple posts and comments here) my own opinion is that there is something not quite right. Whether it is configuration of the servers or routers, or just some performance issues can be problematic to determine. Kinda like troubleshooting a tractor with the mag in one county and the carb in another.
|