OSM applet doesn't work behind proxy's #360
Comments
|
Author: openstreetmap[at]gagravarr.org I think what we want to do is query the browser's proxy configuration, and then pass that into HttpClient when we set it up. Does anyone know how an applet goes about finding the proxy settings in a reliable way? I've seen talk of properties, and of environment variables, so I'm not sure quite how you'd check. |
|
Author: jukka.rahkonen[at]mmmtike.fi I am not a programmer, but perhaps this article I found with search "java applet proxy set" from Altavista is handling something analogous? |
|
Author: osm[at]bcowan.fastmail.co.uk Applet is gone. |
Reporter: Andrew.Rowbottom[at]gmail.com
[Submitted to the original trac issue database at 12.20pm, Thursday, 14th December 2006]
The OSM applet doesn't seem to work for me, I suspect the problem is because I'm behind a proxy and the HTTPClient isn't being set-up to use the proxy. I've tried setting -Dhttp.proxyHost and -Dhttp.proxyPort for my applet JRE, but it still doesn't work.
It might be possible to use other system properties, for example performing a "dump system and deployment properties" in the java console (Java Plug-in 1.6.0-beta2) I get the following properties listed that look like they may be useful:
javaplugin.proxy.config.list = http=proxy.domain.com:80,https=proxy.domain.com:80,ftp=proxy.domain.com:80,gopher=proxy.domain.com:80
deployment.javaws.proxy.http = proxy.domain.com
deployment.javaws.proxy.httpport = 80
deployment.proxy.ftp.host = proxy.domain.com
deployment.proxy.ftp.port = 80
deployment.proxy.http.host = proxy.domain.com
deployment.proxy.http.port = 80
The text was updated successfully, but these errors were encountered: