Last modified: 2014-02-12 23:32:51 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 T46113, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44113 - http proxy support broken
http proxy support broken
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.20.x
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-18 15:48 UTC by buster2
Modified: 2014-02-12 23:32 UTC (History)
5 users (show)

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


Attachments

Description buster2 2013-01-18 15:48:43 UTC
The change from Wed, 29 Feb 2012 in includes/HttpFunction.php broke mediawiki’s proxy support.

see https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=commitdiff;h=1d065d50f63676e081b0101f849aaa0249b950c7;hp=2730e89017079d4675a8ef9d353255661a03a112 in function proxySetup() 

-               if ( $this->proxy && !$this->noProxy ) {

If there is a proxy set AND we should NOT USE proxy then return instantly without setting a proxy.

That sounds reasonable.

+               if ( $this->proxy || !$this->noProxy ) {

If there is a proxy set OR we should NOT USE proxy then return instantly without setting a proxy.
(Correctly) Applying De_Morgan's laws we get:
If there is a proxy set AND we should NOT NOT USE proxy then return instantly without setting a proxy.
Simplifying we get:
If there is a proxy set AND we should USE proxy then return instantly without setting a proxy.

That doesn’t make any sense.
Comment 1 Aaron Schulz 2013-01-18 19:01:19 UTC
I think there is some confusion with lazy loading there. If the proxy is already set, setting it again does nothing. The problem is with the default proxy setting.

The code is way too confusing for what it actually does, but a quick change is proposed in https://gerrit.wikimedia.org/r/#/c/44682/1 for now.
Comment 2 T. Gries 2013-01-18 23:35:20 UTC
I think this is not what I proposed... 

The mechanism was intended to disable a proxy (even if this has been set-up in the Settings) on a url-by-url base by setting noProxy for such urls (in an intranet) where no proxy is needed.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links