jshttp/statuses

documentation is incorrect

zavr-1 opened this issue · 1 comments

the status function will not throw on 306

You are correct. I'm not sure what the preferred fix here would be, making it throw would be a breaking change.

It seems to have snuck in with the IANA codes. The other 3 sources do not recognize 306 as a valid status. IANA lists it because it is a reserved status, but is deprecated.

The docs are indeed inaccurate, though.