Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1360527

Summary: (6.4.z) Accept header matching
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Chao Wang <chaowan>
Component: RESTEasyAssignee: jboss-set
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.9CC: bmaxwell, fgavrilo, jbilek, pmackay, weli
Target Milestone: CR1   
Target Release: EAP 6.4.10   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:57:55 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:
Bug Depends On:    
Bug Blocks: 1324261, 1339868    

Description Chao Wang 2016-07-27 01:55:27 UTC
Resteasy library is being very strict about the "Accepts" header matching. The ODta4J library when it defined the "$metadata" service it defined one of its "accept" headers as "application/xml;charset=utf-8".

When client issues a "$metadata" call for metadata service, the client uses "application/xml" (omits the charset=utf-8) as its "accept" header, Resteasy while matching the requests it does not like it, it expects EXACTLY same header like "application/xml;charser=utf-8" not even allows different case of the header like "applicatoin/xml;charset=UTF-8"

Comment 3 Peter Mackay 2016-08-30 11:00:12 UTC
Verified with EAP 6.4.10.CP.CR2

Comment 4 Petr Penicka 2017-01-17 12:57:55 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.