diff options
author | Eric Wong <e@80x24.org> | 2016-04-06 05:40:21 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2016-04-06 06:22:11 +0000 |
commit | 8c9f33a5396d2792b9bdbdfd785f6feba2fb7514 (patch) | |
tree | 119618ed5f03697f66e7f2286c1887ec986d7626 /Documentation/yahns_config.pod | |
parent | 21f2bb507bd34d263059595802f773481af5416e (diff) | |
download | yahns-8c9f33a5396d2792b9bdbdfd785f6feba2fb7514.tar.gz |
Without this, we could only support persistent connections if the backend gives a valid Content-Length or set "Transfer-Encoding: chunked" in the response header. Being good netizens, we want to use persistent connections as much as possible if a remote client supports it; so perform chunking ourselves when our remote clients are HTTP/1.1 and able to decode chunked responses. This is necessary to support some non-Rack HTTP/1.0-only backend servers which rely on connection termination to terminate responses. Tested manually with a Perl PSGI application running under "plackup". Unlike Rack, the PSGI spec does not specify whether the PSGI application or PSGI server should handle response termination: git clone https://github.com/plack/psgi-specs.git
Diffstat (limited to 'Documentation/yahns_config.pod')
0 files changed, 0 insertions, 0 deletions