* Fixup SERVER_PROTOCOL & HTTP_VERSION headers
HTTP_VERSION header can be defined by a client, but it's also used by Rack, Rails, Sinatra, etc. Change c/ragel code to set SERVER_PROTOCOL to the HTTP protocol defined by the request 'first line', and for now, set HTTP_VERSION to the same.
Note that previously SERVER_PROTOCOL was set to http/1.1, which has been since the start of Puma.
* Tests - replace HTTP_VERSION with SERVER_PROTOCOL
* Fail build if compiling extensions raises warnings (#1953)
Make warning into errors and also fix all compiler warnings reported in
mini_ssl source code.
* Fix some compiler warnings and errors reported by checks
* Add MAKE_WARNINGS_INTO_ERRORS env variable
MAKE_WARNINGS_INTO_ERRORS environment variable toggles whether a build should
treat all warnings into errors or not.
Move appending WERRORFLAG to cflags after OpenSSL methods verification because
on some specifics builds this causes mkmf to wrongly detect methods in OpenSSL
headers.
* Add noentry to write date to avoid unused variables
* Ignore implicit-fallthrough warnings
Those warnings are related to ragel state machine generated code.
* Enforce no warnings on GH Actions
* Update History.md file reflecting latest changes
`rake ragel` failed due to renaming the ragel machine from
`http_parser` to `puma_parser` in 3726b7ef19.
The problem was probably overseen since the file
http11_parser.java.rl has not been touched at this commit
and therefore the rake task did not invoke the parser
generation for the java parser.
* Rename Mongrel to Puma and move files appropriately
* Add HttParser11#body method
* Fix native.rake to not attempt C ext under JRuby
* Mask out all of test_unix_socket.rb under JRuby
