Geoserver - current forced rewriting rule to https prevents from using GeoServer layer preview
|Status:||Closed||Start date:||Nov 28, 2016|
|Assignee:||Andrea Dell'Amico||% Done:|
It seems that redirecting always Geoserver to https prevents from using the GeoServer layer preview (which is the first UI layer admins use for controlling the layer is correctly published). Look at this request: https://geoserver1-spatial-dev.d4science.org/geoserver/aaps/wms?service=WMS&version=1.1.0&request=GetMap&layers=aaps:cage&styles=&bbox=19.903981,35.479604,27.775127,40.554855&width=768&height=495&srs=EPSG:4326&format=application/openlayers and inspect network resources, you will see that OpenLayers css/js http resources are blocked. Maybe the most straighforward would be to let run Geoserver also on http, and not to rewrite systematically to https? (only a suggestion)
@firstname.lastname@example.org, i've assigned this to you since you performed all the previous tasks on moving GeoServer to https secure protocol.
Thanks in advance for looking into that
#2 Updated by Andrea Dell'Amico almost 3 years ago
Can you try setting the
proxy base url as described here? http://docs.geoserver.org/latest/en/user/configuration/globalsettings.html
It should fix the behaviour. If it does not work I'll disable the http -> https redirection.
#3 Updated by Emmanuel Blondel almost 3 years ago
- % Done changed from 0 to 100
It works indeed!
However, still related to https: i have different behavior when querying https://geoserver1-spatial-dev.d4science.org/geoserver vs. what i get from production D4Science geoserver. In the first, i get errors of cross-origin policy (running on localhost). Can you check/compare and confirm that there is no domain constraint to query the newly set-up Geoserver? if they are constraints there should be removed so we can perform OGC WMS/WFS requests. Thanks in advance