Closed jerstlouis closed 1 year ago
When I click on http://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid , I get a valid response. See the attached screenshot. The link worked on both Safari and Chrome.
The second part of the Issue description above is a duplicate of https://github.com/opengeospatial/NamingAuthority/issues/170 and https://github.com/opengeospatial/NamingAuthority/issues/198
@jerstlouis Please move the bullet points to https://github.com/opengeospatial/NamingAuthority/issues/198 and close this GitHub Issue (#197) so that we can keep all relevant comments in the same issue.
@ghobona - I have the same issue as Jerome. In my case the behavior depends on the browser:
Chrome (latest version): When I click on http://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid, I get a 307 redirect due to HSTS to https://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid which in turn results in a 303 redirect to http://defs.opengis.net/vocprez/object?uri=https://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid which returns 400 Bad Request.
This is what I see in the browser:
Firefox: There is no 307 HSTS redirect and I directly get a 303 redirect to http://defs.opengis.net/vocprez/object?uri=http://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid (note: http, not https).
When I try https://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid in Firefox, I also get the 400 error.
Thank you @ghobona .
When I click on http://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid , I get a valid response. See the attached screenshot. The link worked on both Safari and Chrome.
I meant clicking on the See Also, not the URI (that just sends back to the current page).
The second part of the Issue description above is a duplicate of https://github.com/opengeospatial/NamingAuthority/issues/170 and https://github.com/opengeospatial/NamingAuthority/issues/198
Yes I discovered #170 afterwards and was not sure whether it was a duplicate of this issue or not. It was not obvious from the title: External seeAlso references are erroneously sent back to the Definitions Server, but that is indeed what causes this issue.
I have moved the bullet points to #198, and added the other details to #170. Closing this issue.
Clicking see also on any TileMatrixSet e.g.,
http://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid
Results in a 400 Input Error.
The URL that see also links to is e.g.,
https://defs.opengis.net/vocprez/object?uri=http%3A//schemas.opengis.net/tms/1.0/json/examples/GNOSISGlobalGrid.json
This makes it impossible for users/developers to manually retrieve a TileMatrixSet definition from the registry.
However, please note that:
/tms/2.0
, however that should not be relevant because:Related to #170 .