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

Fun idea for a serious problem of bad server HTTP codes #460

Closed

berezovskyi opened this issue Dec 10, 2020 · 1 comment

Labels

Area: Core Core: Main Spec Kind: Enhancement Priority: Low

Member

berezovskyi commented Dec 10, 2020

If you try to request https://polarion.oslc.itm.kth.se/polarion/oslc/services/catalog, the server will serve you a 200 OK and a login page instead of RDF (which breaks ). Putting aside the fact that servers doing so shall be set on fire, I recently discovered by pure chance an ingenous way to deal with it: protocol-registries/well-known-uris#13

To be honest, it's not a fix for all problems but may be a good start:

berezovskyi mentioned this issue

How to work around servers returning wrong HTTP codes OSLC/oslc-browser#17

Open

berezovskyi added Area: Core Core: Main Spec Kind: Enhancement Priority: Low labels

Member Author

berezovskyi commented Feb 6, 2021

Wontfix; no resources + this capability can be added without any spec guidance from our side.

berezovskyi closed this as completed

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