UESPWiki:Administrator Noticeboard/Archives/Server-level Problems
|This is an archive of past UESPWiki:Administrator Noticeboard discussions. Do not edit the contents of this page, except for maintenance such as updating links.|
Daveh, we seem to have a few problems at this point related to server-level configuration. Several of them appear to indicate that there is some type of caching on content1.uesp.net that is being too aggressive, and is providing cached versions of pages that should not be cached (or that do not correspond to the requested page). Specifically:
- The problem with category pages mentioned above
- A persistent problem on the forums where users are told they are banned when they try to login, even though their account is not banned. See for example this topic. This is happening even in cases where the user is using the new forums.uesp.net site name. My guess is that it is actually a caching problem: a cached version of the post-login page is being displayed, instead of processing and creating a newly updated post-login page. This is starting to become a real hassle for forums users.
- A problem on the forums where a new user whose message is spamblocked cannot subsequently post the message, even after all links have been deleted from the message. Again, it sounds like a potential caching problem where the new request is not being recognized as a different request.
In all cases, these problems have been reported even when requests are going directly to content1.uesp.net, so the problem is not with the squid server. Would it be possible to go through the other levels of caching that are implemented directly on content1 (e.g., memcache? apache settings such as gzip? any others?) and selectively disable those caching systems one at a time? You could then check and see whether this link and this link then provide the same page or different pages, allowing the source of one of the problems to at least be identified.
Another problem is with the Oblivion map being inaccessible when using a firewall, as described at Map does not work properly for me. My guess is that firewalls are having a problem with a request sent to www.uesp.net that then triggers followup traffic from content1.uesp.net instead of www.uesp.net . However, the maps cannot be accessed directly on content1.uesp.net because of the Google Maps API license.
- Just a question here, but what does "Cached/caching" mean? The more you ask, the more you learn. Thanks. --Playjex 18:15, 13 March 2008 (EDT)
- For the forums issue I've currently set up a Redirect on content1 to forward www.uesp.net/phpbb to forums.uesp.net, which I should have done in the first place. This should prevent older links from having a cache issue. Whether this fixes anything is another matter...I'm not quite sure how to test it other than waiting to see if anyone else complains. -- Daveh 11:47, 27 March 2008 (EDT)