Hello Lukas,

Thanks for getting back to me.

I'm game to try anything if you all have ideas with Lua or otherwise. We're 
looking at a server that's used less than 1% of our requests, but we need for 
legacy device support. :(

Best,
Luke

—
Luke Seelenbinder
SermonAudio.com <http://sermonaudio.com/> | Senior Software Engineer


> On Jun 26, 2019, at 16:17, Lukas Tribus <li...@ltri.eu> wrote:
> 
> Hello,
> 
> 
> On Wed, 26 Jun 2019 at 16:08, Luke Seelenbinder <l...@sermonaudio.com> wrote:
>> 
>> Hello List,
>> 
>> I have a painful case of noncompliance to report and figure out how to fix.
>> 
>> When HTX is enabled, all headers are returned in lower case (e.g., 
>> content-length, date, etc.). This is obviously fine and within spec. 
>> Unfortunately, I'm using a rather frustrating piece of software (Wowza) that 
>> talks to an haproxy instance and Wowza requires that the content-length 
>> header is always camel case, i.e., Content-Length, otherwise requests fail.
>> 
>> I tried using http-response set-header Content-Length 
>> %[res.hdr(content-length)] if { res.hdr(content-length) -m found } to force 
>> the value to upper case, but that didn't help.
>> 
>> This is very obviously a case of badly behaving software and not a problem 
>> with HAProxy, but I'm wondering if there's any other way to force that 
>> header to Content-Length without turning HTX off.
>> 
>> Thanks for any ideas!
> 
> Yeah I think we are gonna see more of such interoperability issues as
> people migrate to 2.0 with htx enabled:
> 
> https://discourse.haproxy.org/t/haproxy-2-0-0-header/3930/4
> 
> This is only the second time this has come up though.
> 
> 
> Maybe we can workaround this with some LUA magic?
> 
> 
> cheers,
> lukas
> 

Reply via email to