Project

General

Profile

Actions
Copy link

Bug #649

closed

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

Added by Anonymous almost 19 years ago. Updated over 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
mod_proxy
Target version:
-
ASK QUESTIONS IN Forums:

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.

Actions
Copy link
 #1

Updated by stbuehler almost 17 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

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.

Actions
Copy link
 #2

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Invalid
Actions
Copy link

Also available in: Atom