annotate misc/README @ 5304:d3eab5e2df5f
Upstream: no last buffer on errors.
Previously, after sending a header we always sent a last buffer and
finalized a request with code 0, even in case of errors. In some cases
this resulted in a loss of ability to detect the response wasn't complete
(e.g. if Content-Length was removed from a response by gzip filter).
This change tries to propogate to a client information that a response
isn't complete in such cases. In particular, with this change we no longer
pretend a returned response is complete if we wasn't able to create
a temporary file.
If an error code suggests the error wasn't fatal, we flush buffered data
and disable keepalive, then finalize request normally. This allows to to
propogate information about a problem to a client, while still sending all
the data we've got from an upstream.
author |
Maxim Dounin <mdounin@mdounin.ru> |
date |
Thu, 25 Jul 2013 15:00:41 +0400 |
parents |
09dbd363050a |
children |
001beb963d86 |
rev |
line source |
681
|
1
|
|
2 make -f misc/GNUmakefile release
|
|
3
|
|
4 the required tools:
|
|
5 *) xsltproc to build CHANGES,
|
|
6 *) java and XSLScript ( http://pault.com/pault/XSLScript/ ) to build XSLTs
|
|
7 from XSLScript sources.
|
|
8
|
|
9
|
|
10 make -f misc/GNUmakefile icons
|
|
11
|
|
12 the required tool:
|
|
13 *) netpbm to create Win32 icons from xpm sources.
|