On 05/08/2017 01:32 PM, Reyk Floeter wrote: > Hi, > > you cannot disable it and this Android client is broken. > > "A recipient MUST be able to parse and decode the chunked > transfer coding." > > https://tools.ietf.org/html/rfc7230#section-4.1 > > Reyk > Agreed, this Android client is broken, but is it possible to make the "chunked transfer coding" optional, let people choice to compatible broken client like this one?
I tried to manully disable this feature by edit (I'm NOT really know
coding, just try) the code like below,
Index: server_fcgi.c
===================================================================
RCS file: /cvs/src/usr.sbin/httpd/server_fcgi.c,v
retrieving revision 1.74
diff -u -p -u -r1.74 server_fcgi.c
--- server_fcgi.c 21 Jan 2017 11:32:04 -0000 1.74
+++ server_fcgi.c 8 May 2017 05:50:05 -0000
@@ -385,7 +385,8 @@ server_fcgi(struct httpd *env, struct cl
fcgi_add_stdin(clt, NULL);
}
- if (strcmp(desc->http_version, "HTTP/1.1") == 0) {
+ if (strcmp(desc->http_version, "HTTP/1.1") == 0 && \
+ strcmp("my-cloud.domain.com", srv_conf->name) != 0) {
clt->clt_fcgi.chunked = 1;
} else {
/* HTTP/1.0 does not support chunked encoding */
And then this broken Android client work normally.
Please help, thanks.
signature.asc
Description: OpenPGP digital signature
