Bug 849807 - Receive error messages when accessing broker rest api from browser in production
Summary: Receive error messages when accessing broker rest api from browser in production
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OKD
Classification: Red Hat
Component: Master
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Lili Nader
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-21 00:57 UTC by Clayton Coleman
Modified: 2015-05-15 00:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-29 21:29:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Clayton Coleman 2012-08-21 00:57:37 UTC
When I try to access /broker/rest/api.json from my browser I see output.  When I try to access any other resources I get a service error page, probably due to an exception or other bad response from the server.  This works in the devenv.

Also happens with 

  curl -k -u <user>:<pass> https://openshift.redhat.com/broker/rest/domains.json

Can be deferred out of this sprint but this would affect anyone using AJAX to hit the server.

Comment 1 Lili Nader 2012-08-21 01:33:57 UTC
It works for me on openshift.redhat.com.  Can you please add a -i option to your curl request so we can see what HTTP response code you are getting and also the server output.

Comment 2 Clayton Coleman 2012-08-21 03:16:55 UTC
No longer happens in curl, still happening in browser.

Comment 3 Ravi Sankar 2012-08-29 21:25:20 UTC
Tried https://openshift.redhat.com/broker/rest/domains.json,../rest/domains/<dom>.json, .../rest/domains/<dom>/applications.json on commandline using curl and also in browser and it worked as expected.
Clayton, can you tell us which rest api is not working in browser? and whats the error message?

Comment 4 Clayton Coleman 2012-08-29 21:29:33 UTC
Looks to no longer happen in browser.  Error message was purely generic (the 5xx apache error page in production), I couldn't see the logs.

I'll close and reopen if it happens again.


Note You need to log in before you can comment on or make changes to this bug.