Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swagger does not handle error responses #79

Open
kupiakos opened this issue Nov 21, 2016 · 2 comments
Open

Swagger does not handle error responses #79

kupiakos opened this issue Nov 21, 2016 · 2 comments

Comments

@kupiakos
Copy link
Owner

kupiakos commented Nov 21, 2016

For any request that causes a non-200 response, the Swagger page just sits waiting for a response. Chrome sends and receives the request, but the result is not displayed.

@Audakel
Copy link
Contributor

Audakel commented Nov 22, 2016

this is what i am getting http://imgur.com/9KGzCK4
but i am running the server with ant our-server

@Audakel
Copy link
Contributor

Audakel commented Nov 22, 2016

this might be why http://stackoverflow.com/a/37851186
il look at how our server is throwing exceptions

looks like on contentType is not getting set contentType = headers["Content-Type"]; is null in chrome inspector.

Audakel pushed a commit to Audakel/CS340 that referenced this issue Nov 22, 2016
Audakel added a commit to Audakel/CS340 that referenced this issue Nov 22, 2016
Audakel added a commit to Audakel/CS340 that referenced this issue Nov 22, 2016
Audakel added a commit to Audakel/CS340 that referenced this issue Nov 22, 2016
Audakel added a commit to Audakel/CS340 that referenced this issue Nov 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants