Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linked Data enforces HTTPS but has redirects downgrading to HTTP #722

Open
JJ-Author opened this issue Jan 10, 2022 · 2 comments
Open

Linked Data enforces HTTPS but has redirects downgrading to HTTP #722

JJ-Author opened this issue Jan 10, 2022 · 2 comments

Comments

@JJ-Author
Copy link
Contributor

Where did the problem occur (e.g. dbpedia.org/sparql, lookup, spotlight)?

Please give the full URL, if possible

Linked Data interface of dbpedia.org ( http://dbpedia.org/resource/.. )

Problem description

when looking at the redirect chain I identified a problem. Linked Data enforces https but then has a fallback to http which does not make sense to me and can break downloading data. (I remember if you download files with vanilla Java e.g. from the databus/collections (whereas the databus file identifiers use https) you have a problem with files that point to non-https download locations (so original download url is not https. fix applied to solve this dbpedia/dbpedia-databus-collection-downloader@6091021)

http://dbpedia.org/resource/Berlin --[303]--> https://dbpedia.org/resource/Berlin --[303]--> http://dbpedia.org/data/Berlin.ttl -[303]-> https://dbpedia.org/data/Berlin.ttl

Expected behaviour

Fix option 1: https not enforced when rdf mimetypes are requested (for html mimetype https enforcing makes sense and this is probalby what broke it, a wrong lets-encrypt auto setting)
http://dbpedia.org/resource/Berlin --[303]--> http://dbpedia.org/data/Berlin.ttl
Fix option 2: https enforced
http://dbpedia.org/resource/Berlin --[303]--> https://dbpedia.org/resource/Berlin --[303]--> https://dbpedia.org/data/Berlin.ttl

Request/Reproduction

Give the link or request, so the problem can be reproduced. Ideally, this would be a unix curl command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants