-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 22.01.2016 17:31, silvioprog wrote: > Hm... I saw it, but it should be disabled without force this close > header. I'll debug it and try to send a patch... HTTP standard forbids response without "Connection: " line in header. MHD just follow the standard. > On Jan 22, 2016 8:34 AM, "Christian Grothoff" <[email protected] > <mailto:[email protected]>> wrote: > > The way to prevent MHD from automatically setting "Connection: > keep-alive" is to explicitly set "Connection: close". > > On 01/22/2016 04:17 AM, silvioprog wrote: > > Sometimes we need to disable the keep-alive header. For example, > see this [skip] > > Wel, just for a test, I tried to disable it on MHD, but it doesn't > worked. > > I tried with MHD_del_response_header(response, > MHD_HTTP_HEADER_CONNECTION, > > "Keep-Alive") and MHD_del_response_header(response, > > MHD_HTTP_HEADER_CONNECTION, NULL), same problem with both, the > connection > > keep-alive header persists. > > > > So, is the connection keep-alive header sent unconditionally by > MHD? If so, > > it should be configured via flags, so the user (programmer) could > populate > > all headers from a own list instead of removing it from an already > > populated list by the library, avoiding another loop (eg: > > MHD_del_response_header), increasing performance in the end code. > > > > Thank you! > > > - -- Best Wishes, Evgeny Grin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWolpPAAoJEL96xKXqwrr08F8H/0QxHjhO7AovwVCZPLj3QIei ziiMJ2e/RlL2VagpKl1uW8r+HOxP6Zhw5YnL86PNYqI3ah/NBRrt+ECduUkRm9dn wWySg5QZr5ZapZRPVOC4vTSPKpJgTgiLrUQ+aHhsD1nXrWP6MlmU3MmZniCFafd2 6qew8TtwjCc9RLOIyZXXWr1rzy9LMT7DZM3mZ4Thc1lQCyHLqO7zBkFWFMM+7J3a cb/m5N1ESZ9UgqpVEqgsCH332LlleefHOIgadH+vX55Cmbw4Y7wy9I0WGMFID5EQ +SsXbn9aZS2YWpcBVDDMATUVM25l4ArfOqT8bdlVGfV2T9O5v9uGTf1RO1DvQoY= =EZmV -----END PGP SIGNATURE-----
