HTTP_VERSION vs SERVER_PROTOCOL and Rack::Lint about rack HOT 5 CLOSED

For reference, the Lint check was added in caed808

I think the Lint check was added so that apps/middleware that were using HTTP_VERSION as an alias to SERVER_PROTOCOL don't get client-provided information that they might use incorrectly. Maybe that Lint check can be removed? Servers that want to support both Rack 2 and 3 should do: env['SERVER_PROTOCOL'] || env['HTTP_VERSION']

from rack.

@jeremyevans are you proposing to remove caed808#diff-2db485952a203ded9d5ae1301e35d82601b1c2410f914e767b02c4933b7e8a57R302-R305

If so, I'm also okay with that.

from rack.

I think such a lint may still have value, as it pointed me to (maybe) fix Thin:

macournoyer/thin@b4d7946

Thin was blindly overwriting curl -H 'Version: foo' http://1.2.3.4 with the value at the end of the HTTP request line instead of allowing HTTP_VERSION to be foo.

from rack.

@jeremyevans are you proposing to remove caed808#diff-2db485952a203ded9d5ae1301e35d82601b1c2410f914e767b02c4933b7e8a57R302-R305

If so, I'm also okay with that.

Yep, I think that can be removed. Servers should not have to deal with request Version headers specially.

from rack.

Thin was blindly overwriting curl -H 'Version: foo' http://1.2.3.4 with the value at the end of the HTTP request line instead of allowing HTTP_VERSION to be foo.

IMHO, HTTP_VERSION should not be set by the server going forward. I'll add a rack-conform test for this.

As we merged #2154 I believe this issue is resolved, but feel free to re-open it if not.

from rack.