Geoserver refers wms namespaces to an internal URL instead of referring to the official OGC URL within xsd:schemaLocation attribute in the GetCapabilities of WMS
This is allowed following OGC WMS specification but I think it should always be a good practice to reference a resource with the URL of the one that creates it (OGC 's in this case). Moreover I noticed that ESRI clients does not read properly geoserver WMS that use https URL instead of http URL because the local URL is in https and ESRI waits for http URL (which is another problem).
I would replace this first tag in the WMS by the second one
Attachments
3
Activity
Joey O'Dell
April 25, 2025 at 11:33 AM
Thanks for reporting! This is still a problem we experience in 2.26.2.
For WFS services you can enable canonical schema location to fix this, would be great if this was also available for WMS.
Geoserver refers wms namespaces to an internal URL instead of referring to the official OGC URL within xsd:schemaLocation attribute in the GetCapabilities of WMS
This is allowed following OGC WMS specification but I think it should always be a good practice to reference a resource with the URL of the one that creates it (OGC 's in this case). Moreover I noticed that ESRI clients does not read properly geoserver WMS that use https URL instead of http URL because the local URL is in https and ESRI waits for http URL (which is another problem).
I would replace this first tag in the WMS by the second one