Opened 14 years ago

Closed 13 years ago

#360 closed enhancement (wontfix)

OSM applet doesn't work behind proxy's

Reported by: Andrew.Rowbottom@… Owned by: steve@…
Priority: minor Milestone:
Component: applet Version:
Keywords: Cc:


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 =,,,

deployment.javaws.proxy.http = deployment.javaws.proxy.httpport = 80 = deployment.proxy.ftp.port = 80 = deployment.proxy.http.port = 80

Change History (3)

comment:1 Changed 13 years ago by Nick

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.

comment:2 Changed 13 years ago by jukka.rahkonen@…

I am not a programmer, but perhaps this article I found with search "java applet proxy set" from Altavista is handling something analogous?

comment:3 Changed 13 years ago by osm@…

Resolution: wontfix
Status: newclosed

Applet is gone.

Note: See TracTickets for help on using tickets.