You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the spec HTTP/1.1 must be able to handle pipelined requests on the server, even if it chooses never to initiate it or even send back pipelined responses. We should ensure we're able to handle this eventually in order to comply with the HTTP/1.1 spec. It's not a pressing issue since browsers don't pipeline requests, and most client only do so when opting in to — but we should probably get around to this eventually (:
The text was updated successfully, but these errors were encountered:
According to the spec HTTP/1.1 must be able to handle pipelined requests on the server, even if it chooses never to initiate it or even send back pipelined responses. We should ensure we're able to handle this eventually in order to comply with the HTTP/1.1 spec. It's not a pressing issue since browsers don't pipeline requests, and most client only do so when opting in to — but we should probably get around to this eventually (:
The text was updated successfully, but these errors were encountered: