FYI - I am seeing a lot (10-20% of queries) on secure.wikimedia.org
return proxy errors, since the recent outage. I had been hoping it
would just go away, but the rate is still high...
---
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could
On 03/30/2010 11:29 PM, George Herbert wrote:
FYI - I am seeing a lot (10-20% of queries) on secure.wikimedia.org
return proxy errors, since the recent outage. I had been hoping it
would just go away, but the rate is still high...
why you need secure connection?
masti
On Tue, Mar 30, 2010 at 2:35 PM, masti mast...@gmail.com wrote:
On 03/30/2010 11:29 PM, George Herbert wrote:
FYI - I am seeing a lot (10-20% of queries) on secure.wikimedia.org
return proxy errors, since the recent outage. I had been hoping it
would just go away, but the rate is still
On 03/30/2010 11:42 PM, Chad wrote:
masti: Because he chooses to use one, and Wikimedia offers it. Be
helpful or shut up.
I just wonder while it does not offer anything else than normal access.
If you don't want to answer just be polite.
masti
On Tue, Mar 30, 2010 at 23:42, Chad innocentkil...@gmail.com wrote:
George: For what it's worth, it seems to be working fine for me here.
Maybe someone else can replicate...
I've been having the same problems for a while now. A reload usually
fixes the problem, though, so I haven't bothered to
On Tue, Mar 30, 2010 at 3:10 PM, Schneelocke schneelo...@gmail.com wrote:
On Tue, Mar 30, 2010 at 23:42, Chad innocentkil...@gmail.com wrote:
George: For what it's worth, it seems to be working fine for me here.
Maybe someone else can replicate...
I've been having the same problems for a
RobH will be installing a new secure gateway (gilman) shortly. It was
racked some hours ago.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
George Herbert wrote:
FYI - I am seeing a lot (10-20% of queries) on secure.wikimedia.org
return proxy errors, since the recent outage. I had been hoping it
would just go away, but the rate is still high...
Should be fixed now. Apparently someone reduced the request timeout to
5 seconds
