Re: Mapserver behind proxyserver
Edward Mac Gillavry <[email protected]> Wed, 9 Oct 2019 14:13:32 +0000
| Newsgroups | gmane.comp.gis.mapserver.user |
|---|---|
| Message-ID | <AM0PR08MB39888ACAEF963B70298CB5CFD7950@AM0PR08MB3988.eurprd08.prod.outlook.com> |
--===============1986531222882312896== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_AM0PR08MB39888ACAEF963B70298CB5CFD7950AM0PR08MB3988eurp_" --_000_AM0PR08MB39888ACAEF963B70298CB5CFD7950AM0PR08MB3988eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Tijs, That's mainly configurable the MAP metadata and LAYER metadata. Best, Edward ________________________________ From: mapserver-users <[email protected]> on behalf o= f Kler, Tijs de <[email protected]> Sent: Wednesday, October 9, 2019 12:40:50 PM To: [email protected] <[email protected]> Subject: [mapserver-users] Mapserver behind proxyserver Hey All, I am running a mapserver docker container on port 80 using the following do= cker image: https://github.com/PDOK/mapserver-wfs-postgis. For deployment i have to run behind a proxyserver based on HAproxy that tak= es care of ssl encryption. Accessing GetCapabilites (https://acc.dsr.maps.amsterdam.nl/mapserver/wfs?R= EQUEST=3DGetCapabilities&SERVICE=3Dwfs) resolves and returns xml with the a= vailable layers. The layers however contains url references to port 80: > https://acc.dsr.maps.amsterdam.nl:80/mapserver?request=3DGetMetadata&laye= r=3DInvloedsgebied_Metro How does mapserver build the layer urls? Does it use the request header of the GetCapabilities request to construct = it? Or serverside configuration? And if yes, which header fields or environment/config variables are used to= construct the layer URL? Cheers, Tijs De gemeente Amsterdam streeft naar optimale dienstverlening en zorgvuldige = afhandeling van e-mailverkeer. Als een e-mail niet voor u is bestemd, verzo= ekt de gemeente u vriendelijk ons van de juiste adressering op de hoogte te= stellen en de e-mail te verwijderen zonder de informatie te gebruiken en t= e delen met anderen. Voor verdere informatie over de rechten op informatie,= zie https://www.amsterdam.nl/proclaimer. --_000_AM0PR08MB39888ACAEF963B70298CB5CFD7950AM0PR08MB3988eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > </head> <body> <br> Hi Tijs,<br> <br> That's mainly configurable the MAP metadata and LAYER metadata. <br> <br> Best,<br> <br> Edward<br> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> mapserver-users <m= [email protected]> on behalf of Kler, Tijs de <t= [email protected]><br> <b>Sent:</b> Wednesday, October 9, 2019 12:40:50 PM<br> <b>To:</b> [email protected] <[email protected].= org><br> <b>Subject:</b> [mapserver-users] Mapserver behind proxyserver</font> <div> </div> </div> <style> <!-- @font-face {font-family:"Cambria Math"} @font-face {font-family:Calibri} p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif} a:link, span.x_MsoHyperlink {color:#0563C1; text-decoration:underline} a:visited, span.x_MsoHyperlinkFollowed {color:#954F72; text-decoration:underline} span.x_EmailStyle17 {font-family:"Calibri",sans-serif; color:windowtext} .x_MsoChpDefault {} @page WordSection1 {margin:70.85pt 70.85pt 70.85pt 70.85pt} div.x_WordSection1 {} --> </style> <div lang=3D"NL" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"x_WordSection1"> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">Hey All, </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US"> </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">I am running a mapserver dock= er container on port 80 using the following docker image: https://github.co= m/PDOK/mapserver-wfs-postgis. </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US"> </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">For deployment i have to run = behind a proxyserver based on HAproxy that takes care of ssl encryption. </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">Accessing GetCapabilites (htt= ps://acc.dsr.maps.amsterdam.nl/mapserver/wfs?REQUEST=3DGetCapabilities&= SERVICE=3Dwfs) resolves and returns xml with the available layers. </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">The layers however contains u= rl references to port 80:</span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">> https://acc.dsr.maps.ams= terdam.nl:80/mapserver?request=3DGetMetadata&layer=3DInvloedsgebied_Met= ro</span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US"> </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">How does mapserver build the = layer urls?</span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">Does it use the request heade= r of the GetCapabilities request to construct it? Or serverside configurati= on?</span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">And if yes, which header fiel= ds or environment/config variables are used to construct the layer URL?</sp= an></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US"> </span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">Cheers,</span></p> <p class=3D"x_MsoNormal"><span lang=3D"EN-US">Tijs</span></p> </div> <br> <p style=3D"font-size:9pt; font-family:Corbel; color:Grey"><br> De gemeente Amsterdam streeft naar optimale dienstverlening en zorgvuldige = afhandeling van e-mailverkeer. Als een e-mail niet voor u is bestemd, verzo= ekt de gemeente u vriendelijk ons van de juiste adressering op de hoogte te= stellen en de e-mail te verwijderen zonder de informatie te gebruiken en te delen met anderen. Voor verdere in= formatie over de rechten op informatie, zie https://www.amsterdam.nl/procla= imer.<br> <br> </p> </div> </body> </html> --_000_AM0PR08MB39888ACAEF963B70298CB5CFD7950AM0PR08MB3988eurp_-- --===============1986531222882312896== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbWFwc2VydmVy LXVzZXJzIG1haWxpbmcgbGlzdAptYXBzZXJ2ZXItdXNlcnNAbGlzdHMub3NnZW8ub3JnCmh0dHBz Oi8vbGlzdHMub3NnZW8ub3JnL21haWxtYW4vbGlzdGluZm8vbWFwc2VydmVyLXVzZXJz --===============1986531222882312896==--