Hi list, We have a Geoserver (2.5.4 at the moment but the issue appears the same with a 2.10 version) running in a Jetty 9 instance. This Jetty9 has a valid certificate installed. Both http and https are currently active, each can be accessed individually via https://domain (uses port 443) and http://domain (80).
With no Proxy Base Url set in Geoserver admin / global, when sending getCapabilities to https.../geoserver/.. the URL for getfeatureinfo for example is https... : 443. This makes the map requesting the document believe it needs to use its ProxyHost since https://domain:443 is not the same as https://domain. With a Proxy Base Url in Geoserver admin set to https://domain/geoserver getfeatureinfo requests are sent to https://domain/geoserver , not :443, and as such the web map's ProxyHost isn't used, which is good. When using http:// to access the map however the capabilities document still reports https://domain../geoserver , which makes the map try to use the ProxyHost, which it shouldn't. Potential solutions that I see are making the map access a stored getcapabilities document which as had the :443s removed, as well as only using https and setting Geoserver's Proxy Base Url to https://domain/geoserver. Does anyone have any advice to give? Thanks for reading. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-in-jetty9-http-https-reports-https-443-in-capabilities-doc-tp5300436.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
