Comment 1 for bug 1563371

Revision history for this message
Christian Schwede (cschwede) wrote :

I don't think this is a valid bug. Swift does not generate more than 3 digits after the decimal point; in the example above Swift _consumes_ a header with more than 3 digits. The error is on the client side in this case. I can't find a reference in the RFC (https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html) that an application should return a 406 in this case.