Date | Commit message (Collapse) |
|
RFC 7231, section 6.3.5 gives three possible options for what a
server MUST do when sending a 205 status code:
> Since the 205 status code implies that no additional content will be
> provided, a server MUST NOT generate a payload in a 205 response. In
> other words, a server MUST do one of the following for a 205
> response: a) indicate a zero-length body for the response by
> including a Content-Length header field with a value of 0; b)
> indicate a zero-length payload for the response by including a
> Transfer-Encoding header field with a value of chunked and a message
> body consisting of a single chunk of zero-length; or, c) close the
> connection immediately after sending the blank line terminating the
> header section.
rack itself has no control over c), but should leave options
a) and b) available for middleware and application authors.
https://tools.ietf.org/html/rfc7231#section-6.3.6
The older RFC 2616 text was vague and not specific about
what a server should do:
https://tools.ietf.org/html/rfc2616#section-10.2.6
I noticed this from Plack: https://metacpan.org/pod/Plack::Util
This reverts commit 2c5b076aaba6c83ffce8c6c2b5c49085c1abb5a5.
|
|
Add rdoc dependency
|
|
|
|
fix typo
|
|
typo fix
|
|
|
|
|
|
To support minitest 6 and prevent error message from minitest 5.
|
|
`must_be_nil` if expecting nil.
|
|
Change NEWS file into Markdown file extension
|
|
This way GitHub will render it correctly in browser.
|
|
Update example use of Rack::Deflater
|
|
Prevent exception caused by a race condition on multi-threaded servers
|
|
Response headers need not be a hash according to SPEC,
so grab the io_lambda the first time we iterate through
the headers and avoid an extra hash lookup.
|
|
Improve and test SessionHash#fetch
|
|
|
|
|
|
Handle NULL byte in multipart file name
|
|
|
|
|
|
Freeze default session options
|
|
Some code in my app have been accidentally mutating the default session options,
which broke some session behaviour.
It wasn't easy to track that down, so I'd like to suggest that we freeze this hash
to avoid mutation.
|
|
|
|
Remove json gem
|
|
|
|
Try harder when deciding whether to add a new array element
|
|
Dont break on `nil` Authorization header
|
|
Only move to a new entry if the end key is taken; checking only the
top-level key is insufficient.
|
|
|
|
|
|
|
|
Remove unused variable.
|
|
Ref: https://github.com/rack/rack/commit/812ac75b327c9f3d6ff5074def9721bf6f19e1de#commitcomment-425374
|
|
|
|
Move Rack::Request convienence methods to Helpers
|
|
Make ETags great again. Switch for more secure etag generation.
|
|
|
|
Return 400 if Rack::File or Rack::Directory path contains null byte
|
|
Omit response body for HEAD requests to Rack::Directory
|
|
Move `Request#[]` and `Request#[]=` to `Helpers` and deprecate them
|
|
Use last version of MRI Ruby with CI (travis)
|
|
|
|
|
|
|
|
File paths cannot contain null byte characters and methods that do path
operations such as Rack::Utils#clean_path_info will raise unwanted
errors.
|
|
`$?` may be `nil` here, some quirk on 2.4.0-dev. Split it up to fix.
Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
|
|
Fixes #945.
Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
|
|
|
|
improve fragile webrick test
Awkward busy-wait loop, but sufficient to build on.
|
|
|