|
|
|
Sebastian Schmidt created |
|
Issue Type: |
|
|
Affects Versions: |
2.3.5 |
|
Assignee: |
|
|
Components: |
Configuration, WMS |
|
Created: |
17/Sep/13 7:27 AM |
|
Description: |
I think I discovered a bug concering the configuration of external WMS Data Sources. Iâd like to configure a WMS Server somewhere in the Internet as Data source in order to let Geoserver do some caching and reprojection into my favourite CRS. In my Organisation it is required to pass all Internet access through a HTTP Proxy which requires Authentication by the corresponding HTTP Header. So I set up my JVM with the following parameters: -Dhttp.proxyHost=proxy -Dhttp.proxyUser=me -Dhttp.proxyPassword=pwd -Dhttp.proxyPort=8080 â“Dhttp.nonProxyHosts=*.myorganisation.com When creating the new data source the proxy authentication is not taken into account, the Connection test to the capabilities URL (which seems to come somewhere from apache axis) results in a http 407 authentication required error. As a workaround, I needed to configure a datasource pointing to a Capabilites URL inside myorganisation.com. (hence no proxy would be used on Connection Testing). After the WMS Datasource has been saved for the first time, all subsequent Requests do use the proxyPassword and proxyUser parameters from the JVM System properties correctly, it is even possible to change the URL to point to the external WMS Server via the web interface. As it seems, only the first Connection Test on Creation of a remote WMS server datasource needs to be configured to use proxyUser and proxyPassword. The datastore implementation (geotools?) does take these into account correctly. |
|
Environment: |
Jetty Container |
|
Project: |
|
|
Priority: |
|
|
Reporter: |
Critical