Ability for rackup/Rack::Server to accept handler-specific options on the command line
Signed-off-by: raggi <email@example.com>
Backport URI.encode_www_form_component instead.
allow multi-line comments in the config file
…rt of the query string.
…2 Rack can explode when Content-Type is present, but "filename" is not. This is a bug in handling multipart. Apache HTTP Client will provide Content-Type description without filename for form-data, for example. Conflicts: test/spec_utils.rb Signed-off-by: raggi <firstname.lastname@example.org>
…us==204 etc from jjw
…woodard-multipart * 'multipart' of https://github.com/shwoodard/rack: refactor of multipart module Conflicts: test/spec_utils.rb
* master: Add protection against a malformed or malicious HTTP request causing an infinite loop If handler is not to be found, raise initial load error. If autoloading a rack handler by guessing the corresponding ruby file to load, take into account that this ruby file might register the handler properly. Conflicts: lib/rack/utils.rb
Add protection against a malformed or malicious HTTP request causing an infinite loop
This is better than the cgi/util.rb backport: - Faster (https://gist.github.com/952373) - More spec compliant - Doesn't produce warnings if cgi.rb is required elsewhere
Just use CGI.escape/unescape.
It matches the capitalization in rfc2616 and is also faster for Rack::HeaderHash users that also use the canonical capitalization.
No need to create an array and do a lookup on it every time when case/when can be done more efficiently be the runtime.