Using equal? provides consistent results of equality between 1.8, 1.9, and 2.0 when comparing Tempfile objects. In 1.8, == will change the position of the Tempfile. In 1.9+, == compares Tempfiles correctly. In 1.8, eql? compares Tempfiles correctly In 1.9+, t.eql?(t) always returns false
…lemented due to lack of tests. Closes #292.
…ing, added ipv6 loopback and private address ranges to the default regex Signed-off-by: Konstantin Haase <email@example.com>
Signed-off-by: Konstantin Haase <firstname.lastname@example.org>
After this commit, Rack::Request#accept_encoding doesn't raise an exception for invalid Accept-Encoding value. If Rack::Request#accept_encoding may raise an exception, Rack::Middleware::Deflater may also raise an exception. Because Rack::Middleware::Deflater dosn't rescue an exception from Rack::Request#accept_encoding. On the exception case, it seems that either returning "400 Bad Request" or just ignoring invalid value is better behavior. This patch uses the latter solution.
… a port segment to imply 'standard port', not 'use the SERVER_PORT'