Skip to content

response-code-reliability checking for OK Status #24

Open
@battre

Description

@battre

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 ?

Metadata

Metadata

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