Page MenuHomePhabricator

502 proxy error on Secure server
Closed, DeclinedPublic

Description

I'm receiving a 502 proxy error from the secure server for a single url, namely https://secure.wikimedia.org/wikipedia/en/w/index.php?title=Template_talk:Infobox_U.S._county&redirect=no#editprotected

The description is:
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /wikipedia/en/w/index.php.

Reason: Error reading from remote server

Apache/2.2.8 (Ubuntu) mod_fastcgi/2.4.6 PHP/5.2.4-2ubuntu5.7wm1 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g Server at secure.wikimedia.org Port 443

I have no idea what is causing it, and have not yet tried purging, because i wanted to report the issue first.


Version: unspecified
Severity: normal

Details

Reference
bz25271

Related Objects

StatusSubtypeAssignedTask
DeclinedNone
Resolvedbrion
DeclinedNone

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:14 PM
bzimport added a project: HTTPS.
bzimport set Reference to bz25271.
bzimport added a subscriber: Unknown Object (MLST).

Same for https://secure.wikimedia.org/wikipedia/en/wiki/World_War_II

Probably related to the parser timeint out serverside. Still, the request should be available if you refresh the page, but it seems the proxy forces a purged page or something ?

I'm seeing the same thing when trying to view my contributions filtered by namespace. It usually works for namespaces I have very few edits to, e.g. portal talk (5 edits) but almost never for template (103 edits) or category (71) edits. My 8003 article space edits cause it to fail every time I've tried.

William.Allen.Simpson wrote:

See also the reports at Bug 19588 (2009) and Bug 22982 (2010, also reported by Derk-Jan Hartman). Brion merged the former with speed and status Bug 19587, and just closed the latter as WORKSFORME. But it must not be, as the changes of March 2010 were before this report!

wikimedia-bugzilla wrote:

Merge with bug 19587?

The Wikimedia Foundation operation team is rebuilding the HTTPS system from scratch that will solve this bug for good.

HTTPS has been enabled on test some days ago:
http://blog.wikimedia.org/2011/07/19/protocol-relative-urls-enabled-on-test-wikipedia-org/

Therefore, this bug will not be fixed since the architecture is going to be replaced.