diff options
author | Eric Wong <e@80x24.org> | 2016-04-29 07:36:47 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2016-04-29 07:53:54 +0000 |
commit | 4968041a7e1ff90b920704f50fccb9e7968d0d99 (patch) | |
tree | 7cdb96278268ff5dbb74c361b1a9b86ab53978c0 /Documentation | |
parent | d16326723dcbc0a58e5a91078eac6a6058441702 (diff) | |
download | yahns-4968041a7e1ff90b920704f50fccb9e7968d0d99.tar.gz |
Ugh, it sucks that other servers are so tolerant of violations of the Rack spec. Rainbows! had the same problem: https://bogomips.org/rainbows-public/20140704195032.GA13152@dcvr.yhbt.net/
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/yahns-rackup.pod | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/yahns-rackup.pod b/Documentation/yahns-rackup.pod index efdfb6d..6172661 100644 --- a/Documentation/yahns-rackup.pod +++ b/Documentation/yahns-rackup.pod @@ -159,6 +159,16 @@ 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> |