Last modified: 2014-05-18 13:43:06 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66393, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 64393 - Let error responses pass through the proxy if they contain contents
Let error responses pass through the proxy if they contain contents
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-04-24 20:49 UTC by Liangent
Modified: 2014-05-18 13:43 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Liangent 2014-04-24 20:49:08 UTC 
MediaWiki generates useful 404 pages which get caught by the proxy.
Comment 1 Liangent 2014-05-15 09:49:36 UTC 
This blocks development for me currently. Django catches exceptions then displays them using an HTTP 500 page, so no content is left in error.log. However the proxy catches those HTTP 500 pages further, and replaces them with a standard error page, making me unable to see any exception details anywhere.
Comment 2 Liangent 2014-05-15 09:51:16 UTC 
Yuvi, are you a maintainer of the proxy?
Comment 3 Yuvi Panda 2014-05-18 13:43:06 UTC 
Talked about this with Liangent on IRC some more. Currently the nginx proxy intercepts 404s, 403s, 500s, 502s and 503s and displays helpful content instead. This is, by default, useful since it mentions the names of the maintainers. However, sometimes this is frustrating, for the use cases Liangent mentioned.

The proxy should be able to check if there is any content in the HTTP body from the server upstream, and if so just pass it through rather than redirect. In addition, we should edit the default lighty config to not generate ugly 404 pages but just let them pass through with no content in the body as well. 

Now to actually do those things...
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links