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

Handle Aiohttp Exceptions as valid responses #59

Merged

Conversation

pfreixes
Copy link
Contributor

This PR fixes a bug that till now handled all exceptions as just 500,
while valid Aiohttp Exceptions have to be handled as valid responses.

They are used to notify none 2XX responses, perhaps a 401 is notified
with an HTTPUnauthorized exception.

This PR fixes a bug that till now handled all exceptions as just 500,
while valid Aiohttp Exceptions have to be handled as valid responses,
they are used to notify none 2XX responses, perhaps a 401 is notified
with a HTTPUnauthorized exception.
@pfreixes
Copy link
Contributor Author

Please, considere it in WIP I will add some changes. With the current code the Aiohttp exception is never reraised to the upper middlewares.

@pfreixes
Copy link
Contributor Author

Please, considere it in WIP I will add some changes. With the current code the Aiohttp exception is never reraised to the upper middlewares. Better close it, I will reopen it in while

@pfreixes pfreixes closed this May 15, 2018
@pfreixes pfreixes reopened this May 15, 2018
@pfreixes
Copy link
Contributor Author

Without this PR all none 2XX response code are considered 500, so it needs to be fixed. The PR is ready to be reviewed.

Sorry to be late, I've seen that you have already released the 1.1. but most likely this PR will deserve also a new release.

/cc @haotianw465

@haotianw465 haotianw465 merged commit dc55f7c into aws:master May 16, 2018
@pfreixes
Copy link
Contributor Author

Sorry to bother you @haotianw465 , do you have any ETA for the next release?

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

Successfully merging this pull request may close these issues.

None yet

2 participants