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. --- t/git-http-backend.psgi | 1 - 1 file changed, 1 deletion(-) (limited to 't') diff --git a/t/git-http-backend.psgi b/t/git-http-backend.psgi index 8cec7d35..c9607143 100644 --- a/t/git-http-backend.psgi +++ b/t/git-http-backend.psgi @@ -11,7 +11,6 @@ use BSD::Resource qw(getrusage); my $git_dir = $ENV{GIANT_GIT_DIR} or die 'GIANT_GIT_DIR not defined in env'; my $git = PublicInbox::Git->new($git_dir); builder { - enable 'Chunked' if $ENV{TEST_CHUNK}; enable 'Head'; sub { my ($env) = @_; -- cgit v1.2.3-24-ge0c7