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

API does not seem to return error messages for non HTTP 200 responses #70

Closed
lholman opened this issue Apr 3, 2014 · 2 comments
Closed
Assignees
Labels
Milestone

Comments

@lholman
Copy link
Member

lholman commented Apr 3, 2014

Taking a look at the API documentation we can see that we get a WebException and no Body text returned for the 304 (this is also the case for other errors including HTTP 405), this is confirmed using cURL.
Maybe this is linked to #69 too.
Our unit tests don't seem to be having such an issue.

@lholman lholman added this to the MVP milestone Apr 3, 2014
@lholman lholman added the bug label Apr 3, 2014
@lholman lholman modified the milestone: MVP Apr 3, 2014
@lholman
Copy link
Member Author

lholman commented Apr 4, 2014

So, I've identified the issue behind not getting the custom error body back from Additionator hosted on Azure (this is what the API dotnetfiddle code samples hit), it's an IIS setting, commit coming soon.
All detail here http://lloydholman.co.uk/iis-why-you-squashing-my-custom-error-responses/

@lholman
Copy link
Member Author

lholman commented Apr 7, 2014

Fixed here lloydstone/femah.examples@53985e9

@lholman lholman closed this as completed Apr 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant