Skip to content

How to work around servers returning wrong HTTP codes #17

@berezovskyi

Description

@berezovskyi

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions