From bb38f0fcce73904e68d4cde8f9d85e9da2e93013 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 23 May 2016 07:19:45 +0000 Subject: http: chunk in the server, not middleware Since PSGI does not require Transfer-Encoding: chunked or Content-Length, we cannot expect random apps we host to chunk their responses. Thus, to improve interoperability, chunk at the HTTP layer like other PSGI servers do. I'm chosing a more syscall-intensive method (via multiple send(...MSG_MORE) for now to reduce copy + packet overhead. --- script/public-inbox-httpd | 1 - 1 file changed, 1 deletion(-) (limited to 'script') diff --git a/script/public-inbox-httpd b/script/public-inbox-httpd index b29effcc..f19582fa 100755 --- a/script/public-inbox-httpd +++ b/script/public-inbox-httpd @@ -25,7 +25,6 @@ my $refresh = sub { PublicInbox::WWW->preload; my $www = PublicInbox::WWW->new; $app = builder { - enable 'Chunked'; eval { enable 'Deflater', content_type => [ qw( -- cgit v1.2.3-24-ge0c7