On Thursday, June 05, 2014 5:44:49 PM Christian Grothoff wrote: > On 06/05/2014 07:39 PM, Luke Dashjr wrote: > > On Thursday, June 05, 2014 5:37:43 PM Christian Grothoff wrote: > >> What is not possible right now is to force MHD to not generate any > >> "Connection" > >> header; that'd need an API extension. But, try adding "Connection: > >> close" first, > >> and if that somehow fails to show up properly on the wire, please send a > >> testcase > >> and I'll be happy to take a close look at it. > > > > Connection: close (or really *any* Connection header) will also break the > > client in question :( > > Sounds like the kind of software that shouldn't be on any network...
Yeah, unfortunately, this company keeps shipping the hardware without fixing this issue. :( > Anyway, I could imagine having an option like "force_http_10" that > would tell MHD to always close connections after the first request > and never add connection headers. I suppose that might work. > Still, that leaves the question if that should be an option for the > entire HTTP server (all responses) or a per-response option. Per-response seems ideal to me, since I can potentially identify the problematic client by its user agent... ;) Thanks, Luke
