Opened 20 years ago
Last modified 13 years ago
#571 closed defect
[WMS/WFS] Ability to specify a proxy for remote connections — at Initial Version
| Reported by: | dmorissette | Owned by: | mapserverbugs |
|---|---|---|---|
| Priority: | high | Milestone: | 5.2 release |
| Component: | Documentation - MapServer | Version: | 4.1 |
| Severity: | normal | Keywords: | |
| Cc: | mapserver@…, bartvde@…, franck.villoin@…, tjmitchell@…, micheal.arnold@…, pierrick.brihaye@…, jcampanello@…, mko |
Description
We need the ability to specify a proxy when connecting to remote WMS/WFS servers. This could possibly be added as layer metadata wms_proxy_*, but I wonder if we should instead create global configuration parameters inside the WEB object? I never really worked in environments with proxies, so I wonder if it is safe to assume that when someone uses a proxy, then they use it for *all* their http connections and not only to get to specific hosts? i.e. is it a good idea to have a single global proxy setting in the web object in the mapfile or should this be local at the layer level?
Note:
See TracTickets
for help on using tickets.
