Skip to content
This repository has been archived by the owner on Feb 6, 2020. It is now read-only.

CheStarter returns a 400 error code to fabric8-wit when the error is a 401 http error #204

Open
hectorj2f opened this issue Jul 25, 2017 · 5 comments
Assignees
Labels

Comments

@hectorj2f
Copy link
Contributor

CheStarter is returning a 400 Bad Request error code but the underlying exception is 401 Unauthorized due to OSO token expired.

You can search in dsaas-preview logs for status:500 or for instance req_id: 8136f380-7196-4d21-b050-a0dd948c4800 in Kibana

related to: fabric8-services/fabric8-wit#1538

@hectorj2f hectorj2f changed the title CheStarter returns a 400 error code to fabric8-wit when it gets a 401 http error CheStarter returns a 400 error code to fabric8-wit when the error is a 401 http error Jul 25, 2017
@ibuziuk ibuziuk self-assigned this Jul 25, 2017
@ibuziuk
Copy link
Member

ibuziuk commented Jul 25, 2017

@hectorj2f yeah, this is because of the fact that Bad Request response is used when HttpClientErrorException occurs. Need to provide better handling

[1] https://github.com/redhat-developer/che-starter/blob/master/src/main/java/io/fabric8/che/starter/exception/GlobalExceptionHandler.java#L54

@hectorj2f
Copy link
Contributor Author

@ibuziuk what is the state of this issue ?

@ibuziuk
Copy link
Member

ibuziuk commented Aug 14, 2017

@hectorj2f haven't started working on it and did not add to the current sprint. Is it critical ?

@hectorj2f
Copy link
Contributor Author

@ibuziuk I just want it to be sure it wasn't solved 👍

@hectorj2f hectorj2f reopened this Aug 15, 2017
@ibuziuk
Copy link
Member

ibuziuk commented Aug 15, 2017

@hectorj2f nope, it was not - I will try to find some time to address it though ;-)

@ibuziuk ibuziuk added bug and removed important labels Nov 8, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants