Ticket #649 (closed defect: invalid)

Opened 2 years ago

Last modified 3 weeks ago

mod_proxy more tolerant to \n\n after http response header.

Reported by: anonymous Assigned to: jan
Priority: normal Milestone:
Component: mod_proxy Version: 1.4.11
Severity: normal Keywords:
Cc: Blocking:
Need Feedback: 0

Description

Some web server response requests with \n\n (unix) or maybe \r\r(mac?) instead of the standard \r\n\r\n as the seperator between repsonse header and content. mod_proxy will fail to recognize the broken sites. Can we add check for \n\n and \r\r to work around this?

In mod_proxy, proxy_demux_response.

Attachments

Change History

04/25/2008 01:57:18 PM changed by stbuehler

  • status changed from new to closed.
  • resolution set to invalid.
  • blocking changed.
  • pending changed.

We accept cgi sending \n\n; but i don't think we will mess with the response parsing in 1.4.x (1.5.x has a clean parser to do this). If a web server doesn't use \r\n, you really shouldn't use it.

Anyway, this is not a bug.

Add/Change #649 (mod_proxy more tolerant to \n\n after http response header.)




Change Properties
Action