Bug 1399681

Summary:	Error AH01070 is recorded when a 304 response is fetched from a backend via mod_proxy_fcgi
Product:	Red Hat Enterprise Linux 7	Reporter:	George Notaras <gnot>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED CURRENTRELEASE	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	jorton, luhliari
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-07 09:43:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description George Notaras 2016-11-29 14:49:26 UTC

Description of problem:

The following error is recorded in the httpd error_log, if a 304 response is returned from an fcgi backend:

  AH01070: Error parsing script headers

Please see the following bug report, which refers to a patch that fixes the issue:

  https://bz.apache.org/bugzilla/show_bug.cgi?id=57198

Version-Release number of selected component (if applicable):

httpd-2.4.6-40.el7.centos.4.x86_64

How reproducible:

1. Send a request containing a 'If-Modified-Since' header in order to trigger a 304 response from a backend server with which httpd communicates through mod_proxy_fcgi.
2. See error recorded in error_log

Additional info:

https://bz.apache.org/bugzilla/show_bug.cgi?id=57198

Comment 2 George Notaras 2017-01-17 23:35:23 UTC

I had filed this bug report while using CentOS 7.2. I've now corrected the version above.

Also, after upgrading to CentOS 7.3.1611 (httpd-2.4.6-45.el7.centos.x86_64), I can no longer reproduce the error.

Please, feel free to close this report.

George

Comment 3 Joe Orton 2017-02-07 09:42:44 UTC

Thank you for taking the time to report this issue to us. We appreciate the
feedback and use reports such as this one to guide our efforts at improving our
products. That being said, this bug tracking system is not a mechanism for
requesting support, and we are not able to guarantee the timeliness or
suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket
through the regular Red Hat support channels to ensure it receives the proper
attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please
visit: https://www.redhat.com/en/services/support