Bug 629552

Summary: Proxy should allow all header from rfc2616
Product: [Community] Spacewalk Reporter: Miroslav Suchý <msuchy>
Component: Proxy ServerAssignee: Miroslav Suchý <msuchy>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: spacewalk-proxy-1.3.1-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 656077 (view as bug list) Environment:
Last Closed: 2011-02-08 08:41:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 653453, 656077    

Description Miroslav Suchý 2010-09-02 10:09:02 UTC 
Description of problem:
In commit 90b5ee52536c573227464260feb109fdb5b8a685 we filter only "good" headers. That was because wsgi bloat headers with a lot of garbage.
But currently we only allow X-*, 'content-length', 'user-agent', 'content-type', 'range'.
We should definitely allow other headers (like Last-Modified, If-Range...). In other words we should allow all headers from  rfc2616.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Comment 1 Jan Pazdziora (Red Hat) 2010-10-27 08:32:26 UTC 
Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.
Comment 2 Jan Pazdziora (Red Hat) 2010-11-19 16:05:06 UTC 
Mass-moving to space13.
Comment 3 Miroslav Suchý 2010-11-20 00:17:39 UTC 
fixed in commit 4aca0eaac4c36bc18c4a2c3c6755b5fa8def388c
Comment 4 Tomas Lestach 2011-02-03 12:21:28 UTC 
Moving ON_QA ...
Comment 5 Tomas Lestach 2011-02-08 08:41:17 UTC 
This bug has been fixed in Spacewalk 1.3.