Re: Case Sensitive Headers

Hi Christopher, That's great! Thank you. It looks exactly like what we need. Best, Luke — Luke Seelenbinder SermonAudio.com | Senior Software Engineer > On Jul 25, 2019, at 09:18, Christopher Faulet wrote: > > Le 12/07/2019 à 13:26, Luke Seelenbinder a écrit : >

Re: Case Sensitive Headers

Le 12/07/2019 à 13:26, Luke Seelenbinder a écrit : Hi Christopher, That definitely is ugly—but it works. Thanks! I'll look for improvements in 2.1. Hi Luke, FYI, a feature has been added in the 2.1 to change the case of header names. Take a look on the commit 98fbe953: http://git.haprox

Re: Case Sensitive Headers

Hi Christopher, That definitely is ugly—but it works. Thanks! I'll look for improvements in 2.1. Best, Luke — Luke Seelenbinder SermonAudio.com | Senior Software Engineer > On Jul 10, 2019, at 14:53, Christopher Faulet wrote: > > Le 10/07/2019 à 13:08, Luke Seelenbind

Re: Case Sensitive Headers

Le 10/07/2019 à 13:08, Luke Seelenbinder a écrit : > Hi Patrick, > > That didn't work (in a few different forms I tried)—thanks for the suggestion > though! > > It seems HTX is pretty picky about how those headers get emitted. :) > > I'm still looking for a solution to this that doesn't involve

Re: Case Sensitive Headers

EDT > To: HAProxy <mailto:haproxy@formilux.org> > Subject: Case Sensitive Headers > >> 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., &

Re: Case Sensitive Headers

*From:* Luke Seelenbinder [mailto:l...@sermonaudio.com] *Sent:* Wednesday, June 26, 2019, 10:07 EDT *To:* HAProxy *Subject:* Case Sensitive Headers Hello List, I have a painful case of noncompliance to report and

Re: Case Sensitive Headers

Hi Lukas, Wowza actually talks to a service behind HAProxy, so it should be http-response, because Wowza expects to see "Content-Length" vs "content-length" header from the response served through HAProxy. Best, Luke — Luke Seelenbinder SermonAudio.com | Senior Softwa

Re: Case Sensitive Headers

Hello Luke On Wed, 26 Jun 2019 at 16:08, Luke Seelenbinder wrote: > 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 should be http-request though, not http-

Re: Case Sensitive Headers

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

Re: Case Sensitive Headers

Hello, On Wed, 26 Jun 2019 at 16:08, Luke Seelenbinder 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 s

Case Sensitive Headers

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)