search

dret / I-D

Internet Drafts I've authored or contributed to.
16 stars 13 forks source link

content-warning: should we tie it to the http status code? #135

Closed ioggstream closed 4 years ago

ioggstream commented 4 years ago

Note

The spec says

the response status code SHOULD be in the 2xx range

Q: do we need to tie this header to the http status code?

andrecedik commented 4 years ago

Well, as you pointed out, we're saying that the response could should be in the 2xx range. This is due to the fact, that the original intent was successful, but unfortunately something (else) also happened that the agent should know about. So the request actually was successful - it just has side conditions.

I've added a side note with this commit. To make this clearer.