[#3057] - [#30941] Adding Proxy support to Joomla
- Closed
- 31 Mar 2014
- Medium
- Build: staging
- # 3057
- Diff
- Bakual:CleanProxy
- Foreign ID 30941
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Same as #1685, but cleaned up and against staging.
Issue
Joomla can't connect to update servers or any other extern URL if its webserver is behind a proxy. This is often the case in corporate enviroments.
Solution
This PR will add new parameters to the global configuration which allows to specify a proxy server, port, username and password.
If enabled, it will restrict JHttp to only use curl by default and curl will be told to use the proxy settings.
Tracker
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=30941
| Title |
|
||||||
| Title |
|
||||||
Copyright updated.
Testing the function is not really possible if you don't have such a network at hand.
What you can test is that nothing breaks if the feature is turned off.
Also, you could testas Thomas suggests in the tracker tiem
If you can't setup such a system yourself, then it's probably only possible to test it "reverse": Set an inexistent proxy address and see if it breaks fetching the update information. It should probably timeout then because it doesn't find the proxy server.
If your testing on a localhost, you could instead also use a sniffer software to see where the request is sent to.
It appears that some of the HTTP proxies at http://www.hidemyass.com/proxy-list/search-225371 do support this.
My tests of this PR are good, and with the other feedback on the tracker, I'm comfortable with this being RTC.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-03-31 14:46:01 |
See Copyright date => 2014
Anyway to test this locally?