Hi I'm not sure if this is a recent switch to http://standards.iso.org/ or something I've only noticed now, but it now redirects to the HTTPS protocol from HTTP. For our GeoServer development this is causing problems for the app-schema-cache.
For example, if my namespace schemas are as follows: <Namespace> <prefix>cit</prefix> <uri>http://standards.iso.org/iso/19115/-3/cit/1.0</uri> </Namespace> <Namespace> <prefix>gco</prefix> <uri>http://standards.iso.org/iso/19115/-3/gco/1.0</uri> </Namespace> <Namespace> <prefix>mrl</prefix> <uri>http://standards.iso.org/iso/19115/-3/mrl/1.0</uri> </Namespace> And I include the following target types: <FeatureType> <schemaUri> http://standards.iso.org/iso/19115/-3/mrl/1.0/mrl.xsd </schemaUri> </FeatureType> <FeatureType> <schemaUri> http://standards.iso.org/iso/19115/-3/cit/1.0/cit.xsd </schemaUri> </FeatureType> I get an error when GeoServer tries to build the app-schema-cache 2019-01-15 10:16:35,439 WARN [org.geotools.xml.resolver] - Unexpected response "302 Found" while downloading http://standards.iso.org/iso/19115/-3/mrl/1.0/mrl.xsd It seems the standards.iso.org server redirects GeoServer from one protocol to the next, but GeoServer does not follow, as per the rules of 302. I thought I could fix it by changing the protocol in the included target types from HTTP to HTTPS, eg: <FeatureType> <schemaUri> https://standards.iso.org/iso/19115/-3/mrl/1.0/mrl.xsd </schemaUri> </FeatureType> <FeatureType> <schemaUri> https://standards.iso.org/iso/19115/-3/cit/1.0/cit.xsd </schemaUri> </FeatureType> However, this is only a superficial fix. Because those XSDs themselves import other XSDs from HTTP URIs at standards.iso.org, we are back to where we started and get errors like: WARN [org.geotools.xml.resolver] - Unexpected response "302 Found" while downloading http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19136_Schemas/gml.xsd Is there a setting in GeoServer which forces the following of redirects (or a VM option), or is this something that must be set in the Java code? Thanks Michael Sexton UNCLASSIFIED Classified by [email protected] on 15/01/2019 10:44:31 AM Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks. -------------------------------------------------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
