New Tests - Range, date, 205 #46
Description
Range only for GET (RFC 9110 §14.2)
"A server MUST ignore a Range header field received with a request method that is unrecognized or for which range handling is not defined."
Send POST / HTTP/1.1 with Range: bytes=0-10. Server should process normally (ignore Range). Not tested.
HTTP-date format acceptance (RFC 9110 §5.6.7)
"A recipient that parses a timestamp value in an HTTP field MUST accept all three HTTP-date formats."
Send conditional request with If-Modified-Since using RFC 850 format (Sunday, 06-Nov-94 08:49:37 GMT) and asctime format (Sun Nov 6 08:49:37 1994). Server should accept both.
205 must have no content (RFC 9110 §15.3.6)
Only testable if a server actually returns 205, which is rare.
Upgrade in HTTP/1.0 must be ignored (RFC 9110 §7.8)
"A server that receives an Upgrade header field in an HTTP/1.0 request MUST ignore that Upgrade field."
Send HTTP/1.0 request with Upgrade: websocket + Connection: Upgrade. Server must not return 101.
Precondition evaluation order (RFC 9110 §13.2.2)
"A recipient cache or origin server MUST evaluate the request preconditions in the following order: If-Match, If-Unmodified-Since, If-None-Match, If-Modified-Since, If-Range."
Complex multi-header test to verify correct precedence.