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. --- Documentation/yahns-rackup.pod | 10 ---------- examples/yahns_rack_basic.conf.rb | 6 ------ 2 files changed, 16 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> diff --git a/examples/yahns_rack_basic.conf.rb b/examples/yahns_rack_basic.conf.rb index 610a482..f3f8e6a 100644 --- a/examples/yahns_rack_basic.conf.rb +++ b/examples/yahns_rack_basic.conf.rb @@ -30,12 +30,6 @@ worker_threads 50 end -# note: Rack requires responses set "Content-Length" or use -# "Transfer-Encoding: chunked". Some Rack servers tolerate -# the lack of these, yahns does not. Thus you should load -# Rack::Chunked and/or Rack::ContentLength middleware in your -# config.ru to ensure clients know when your application -# responses terminate. app(:rack, "config.ru", preload: false) do listen 80 -- EW -- unsubscribe: yahns-public+unsubscr...@yhbt.net archive: https://yhbt.net/yahns-public/
