Bug 1324208

Summary: 406's returned from broker api outside of web browser
Product: OpenShift Online Reporter: Rory Thrasher <rthrashe>
Component: MasterAssignee: Rory Thrasher <rthrashe>
Status: CLOSED WONTFIX QA Contact: Wei Sun <wsun>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 2.xCC: aos-bugs, gmillard, gpei, jokerman, mmasters, mmccomas, tiwillia, wsun
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1322543 Environment:
Last Closed: 2017-05-31 18:22: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:
Bug Depends On: 1322543    
Bug Blocks:    

Comment 1 Rory Thrasher 2016-04-05 20:05:03 UTC 
QE,

Before working on the enterprise version of this bug, let's verify that it works with the latest origin-server code.

This fix has had quite a lot of trouble passing tests.  The test failures look to be unrelated, as they also fail without this change.  Just to be safe though, can we do regression tests in addition to verification?

1) Curling the REST api with no header specified returns a successful 200.

$ curl -Ik https://localhost/broker/rest/api

2) Curling the REST api with a non-json header returns successfully using the specified header.

$ curl -H "accept:application/xml" -Ik https://localhost/broker/rest/api

3) Curling while specifying a */* header will successfully return (should return json).

$ curl -H "accept:*/*" -Ik https://localhost/broker/rest/api


4) Regression tests to verify that this change doesn't break the REST api.


Thank you
Comment 3 weiwei jiang 2016-04-11 02:15:35 UTC 
Checked with devenv_5783, and can not reproduce this issue.
Comment 4 Rory Thrasher 2016-05-10 20:50:17 UTC 
*** Bug 1334902 has been marked as a duplicate of this bug. ***
Comment 6 Eric Paris 2017-05-31 18:22:11 UTC 
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.