Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   HTTP headers should be parsed case insensitive, posted by André on Mon Jul 22 16:17:55 2024 
    icon2.gif   Re: HTTP headers should be parsed case insensitive, posted by Stefan Ritt on Wed Jul 31 14:21:21 2024 
Message ID: 69817     Entry time: Wed Jul 31 14:21:21 2024     In reply to: 69807
Icon: Reply  Author: Stefan Ritt  Author Email: I cstefan.ritt@psi.ch 
Category: Bug report  OS: All  ELOG Version: 3.1.5 
Subject: Re: HTTP headers should be parsed case insensitive 

I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?

Stefan

André wrote:

I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.

As stated in the manual, haproxy rewrites all headers to lower case.

elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.

For now I'm using the workaround from the manual:

global
  h1-case-adjust content-length Content-Length
  h1-case-adjust content-type Content-Type

backend elog
  option h1-case-adjust-bogus-server
  server elog 127.0.0.1:8080

But as the manual states, this should not be  used as a permanent solution.

 

ELOG V3.1.5-3fb85fa6