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.

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

response-code-reliability checking for OK Status #24

Open
battre opened this issue Jun 15, 2020 · 0 comments
Open

response-code-reliability checking for OK Status #24

battre opened this issue Jun 15, 2020 · 0 comments
Assignees
@hober @rmondello

Comments

@battre
Copy link

battre commented Jun 15, 2020

The response-code-reliability proposal says: If response’s status is an ok status, reject p. Otherwise, resolve p.

Is this ideal? E.g. error codes like 502 Bad Gateway or 503 Service Unavailable don't positively indicate that /.well-known/resource-that-should-not-exist-whose-status-code-should-not-be-200 behaves like expected.

Should we change the spec to look for /.well-known/resource-that-should-not-exist-whose-status-code-should-be-404 ?
@w3c w3c deleted a comment Jul 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hober hober

@rmondello rmondello

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hober @rmondello @battre