Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Processing doesn't work behind authenticated proxy (update checks, library manager...) #1476
Original author: eoin.ros...@gmail.com (December 04, 2012 16:47:50)
Or maybe this is a feature request for a processing.exe flag to use system proxy, I have no idea what I'm doing.
Also would be awesome if the library updater could consider those unfortunate souls behind corporate proxies when it is implemented.
What steps will reproduce the problem?
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
Note: Please do not link to locations on other sites, such as your own
Original issue: http://code.google.com/p/processing/issues/detail?id=1438
referenced this issue
Feb 15, 2013
Added to preferences.txt for the next release (whatever comes after 2.0.1).
You'll need to add the proxy.host and proxy.port lines to preferences.txt.
More details here, which might help with how to use this for exported apps:
Seems like setting
Steps to reproduce (the simpliest way without having working proxy server to test):
First I thought that proxy support simply wasn't included in 2.0.2 release, however the commit which adds proxy support f88c10e was made on the 7 August, and processing 2.0.2 was released 14 August 2013. So it seems that this commit should have been included into 2.0.2.
Also seems like #2026 is related to this issue somehow. Seems that similar stacktrace can be triggered not only by "Library download", but in more broad sense by PDE trying to access some URL (Tool list , library list, contributions.txt)