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.

Sign up for GitHub

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

Jump to bottom

How to work around servers returning wrong HTTP codes #17

Open

berezovskyi opened this issue Dec 10, 2020 · 0 comments

Member

berezovskyi commented Dec 10, 2020

https://polarion.oslc.itm.kth.se/polarion/oslc/services/catalog returns 200, for example and gives you a login page.

One approach is to request https://polarion.oslc.itm.kth.se/.well-known/resource-that-should-not-exist-whose-status-code-should-not-be-200 beforehand (see protocol-registries/well-known-uris#13 and oslc-op/oslc-specs#460) but it only shows if the server is completely off its meds.

Should we go radical and consider any non-RDF response to be an error?

@jamsden @jadelkhoury

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