search

INSPIRE-MIF / helpdesk-registry

Community for the discussion of change proposals by the submitting organisations for the central INSPIRE registers and register federation and their resolution by the control body.
3 stars 0 forks source link

HTTP redirects to downloaded content not applied, downloads fail #102

Open nmtoken opened 1 month ago

nmtoken commented 1 month ago

Related to https://github.com/INSPIRE-MIF/helpdesk-registry/issues/95 where the suggestion was to use Edge browser...

I'm using Edge and have the same issue.

For example on page: https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory/infoManagementService

The links for available formats are all http://

XML Registry XML ISO 19135 RDF/XML JSON CSV ATOM ROR

and clicking on the link results in browser refusing to download unsafe content.

workaround is to copy and amend the link, but fix would be to change the link in the page to omit the protocol like :// so http goes to http and https goes to https

iratigarzon commented 1 month ago

Dear @nmtoken,

Thank you for the proposal. We will consider changing the link depending on the protocol the user is accessing with. In the meantime, I will provide some screenshots to guide you on downloading the format using Edge.

When you click on the download icon, the following message will appear: "infoManagementService.en.rdf can't be downloaded securely."

Captura de pantalla 2024-07-11 091259

However, if you right-click on the message, you will see three dots with more options. One of these options is to keep the file.

captura2

Click on "Keep" to start the download.

Best regards,

Irati

nmtoken commented 1 month ago

@iratigarzon thanks for pointing out that there is an alternative workaround around for the issue, using Edge. It is though an issue.

Most users will expect that when they click on a link to download content from an EU registry they will be able to trust the result and not get a warning.

nmtoken commented 1 month ago

fix would be to change the link in the page to omit the protocol like :// so http goes to http and https goes to https

Apologies, looking at an example I have it would actually be // not :// at the beginning of the URL.

Consider the following test page:

If I browse it as http://ogc.bgs.ac.uk/BGS_ESA_EN_Terrafirma/ the example ogcapi link takes me to http://ogc.bgs.ac.uk/cgi-bin/TFL-PSI/ows/tfl0/ogcapi and if I browse it as https://ogc.bgs.ac.uk/BGS_ESA_EN_Terrafirma/ the link takes me to https://ogc.bgs.ac.uk/cgi-bin/TFL-PSI/ows/tfl0/ogcapi

We have in the source HTML (line 38) <p><b>Home</b> <a href="//ogc.bgs.ac.uk/cgi-bin/TFL-PSI/ows/tfl0/ogcapi">//ogc.bgs.ac.uk/cgi-bin/TFL-PSI/ows/tfl0/ogcapi</a></p>