Lighttpd

gstrauss wrote:

can not change the request to the backend from HTTP/1.0 to HTTP/1.1

Indeed, that is a stupid overreach, please ignore it, it should not be useful to general audience. IIRC it was driven by some picky backends that did not want to process lighty's proxified requests unless they were marked HTTP/1.1. While sloooowly rebasing a series of ancient patches to 1.4.43, I eagerly submitted this kludge too. My apologies. :-(

patch might break existing usage, since current users are not expecting that value to suddenly override the Host header provided by the client.
For this patch to be considered, the behavior introduced by your patch would need to be made optional behavior, and disabled by default.

I doubt there are users counting on Host to exist while talking HTTP/1.0 (i.e. instead of using the provided X-Host - but that's kinda new too, I don't remember it being there), but anyway, I fully agree it's safer to hide it behind a switch. Thanks. :-)

Thanks for the updated patch.

Would you be averse to me renaming the directive to something shorter, such as "proxy.replace-http-host"?
Should the HTTP Host be forced, even when one is not provided in the original request? (I think it should.)

gstrauss wrote:

Would you be averse to me renaming the directive to something shorter, such as "proxy.replace-http-host"?

Name it whatever you like, configuration parameter brevity was not my goal, I tried to use something that is as self-explanatory as possible.

Should the HTTP Host be forced, even when one is not provided in the original request? (I think it should.)

The Host header provided in the original request is inconsequential for this feature: backends shall receive the name (as Host header) if it's configured as such. Hence, I don't reckon enforcing to be necessary.