On 11/12/12 03:13, Dave Humphrey wrote:
A strange issue we've just noticed between
Special:Random and Squid, at
least so it appears. When accessed directly from the Apache server the
Special:Random works fine but when accessed through Squid we get a blank
page (500 error).
Works:
http://content1.uesp.net/wiki/Special:Random
http://www.uesp.net/wiki/Special:Random?
http://uesp.net/wiki/Special:Random (? see below)
Doesn't Work:
http://www.uesp.net/wiki/Special:Random (how it is usually accessed)
Purging the page from Squid does nothing and it doesn't appear to be a
local client cache issue. The strange thing is when accessing "
www.uesp.net/wiki/Special:Random" through Squid it results in a
TCP_NEGATIVE_HIT/500 but through "uesp.net/wiki/Special:Random" gives the
expected TCP_MISS/302. Both domains resolve to the same IP (the Squid box)
and aren't handled any differently (that I know of anyways).
Thoughts on what I'm missing are welcome....
The 500 error has the headers:
Expires: Sun, 16 Dec 2012 15:02:46 GMT
Cache-Control: max-age=604800
So
http://www.uesp.net/wiki/Special:Random fails while the other
variations work because there is a cached answer for that url.
I see that url as a HIT, not as a TCP_NEGATIVE_HIT, though.
X-Cache-Lookup: HIT from squid1.uesp.net:80
I don't know why purging is not working for you (it should fix it) or
how that page arrived there to begin with.