diff options
author | Eric Wong <e@80x24.org> | 2016-08-03 03:06:25 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2016-08-03 03:06:25 +0000 |
commit | 013d24d62f65368a2f6fdeef2e4680c5345e6992 (patch) | |
tree | f0aa8c2311bf420fc30d5162c4b29b798e92c1bb /Documentation | |
parent | f1f430323bcab90bdbbe980d6ef5b60602796a55 (diff) | |
download | yahns-013d24d62f65368a2f6fdeef2e4680c5345e6992.tar.gz |
Actually, I guess I misread, rack (starting at) 1.0 stopped requiring Content-Length/Chunked headers but I never noticed. Oh well. This reverts commit 4968041a7e1ff90b920704f50fccb9e7968d0d99.
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/yahns-rackup.pod | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/Documentation/yahns-rackup.pod b/Documentation/yahns-rackup.pod index 6172661..efdfb6d 100644 --- a/Documentation/yahns-rackup.pod +++ b/Documentation/yahns-rackup.pod @@ -159,16 +159,6 @@ The RACK_ENV variable is set by the aforementioned -E switch. If RACK_ENV is already set, it will be used unless -E is used. See rackup documentation for more details. -=head1 CAVEATS - -yahns is strict about buggy, non-compliant Rack applications. -Some existing servers work fine without "Content-Length" or -"Transfer-Encoding: chunked" response headers enforced by Rack::Lint. -Forgetting these headers with yahns causes clients to stall as they -assume more data is coming. Loading the Rack::ContentLength and/or -Rack::Chunked middlewares will set the necessary response headers -and fix your app. - =head1 CONTACT All feedback welcome via plain-text mail to L<mailto:yahns-public@yhbt.net> |