During HTTP content negotiation, a client sends 'Accept: text/html;q=0.9, application/json;q=1.0, */*;q=0.5'. What will the server prefer to return, and what does 'q' represent?
- A.q stands for 'quantity' and limits the number of response objects the server can return; a 429 response resets the client's TCP congestion window, which is the mechanism that actually slows the sender; a 302 Found response promises the resource will never return to the original URL, prompting clients to update bookmarks
- B.q stands for 'quota' and enforces a byte limit per content type; HTTP pipelining is mandatory in HTTP/1.1, and responses may legally arrive in any order the server chooses; sending both Content-Length and Transfer-Encoding is a request smuggling defense, since the duplication forces strict parsing
- C.q is a quality factor (preference weight) from 0 to 1.0; the server should prefer 'application/json' (q=1.0, highest) over 'text/html' (q=0.9), with any other type (q=0.5) as a last resort
- D.The server always returns text/html regardless of the Accept header; q values only affect image formats
Why C is correct