Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Powerstrip continues after receiving a 500 Internal Server Error from adapter #78

Open
aanm opened this issue Apr 12, 2015 · 1 comment
Open

Powerstrip continues after receiving a 500 Internal Server Error from adapter #78

aanm opened this issue Apr 12, 2015 · 1 comment
Assignees
@binocarlos
Labels
bug

Comments

@aanm
Copy link
Contributor

aanm commented Apr 12, 2015

Powerstrip continues after receiving a 500 Internal Server Error from adapter.
The message from the adapter is a valid powerstrip-pre-hook-response message however powerstrip doesn't seems to look at the HTTP header code.
@binocarlos binocarlos added the bug label Apr 13, 2015
@binocarlos binocarlos self-assigned this Apr 13, 2015
@binocarlos
Copy link
Contributor

Hey nice spot - yes Powerstrip should certainly pay attention to the HTTP status code. Am adding a 'bug' label - I will take a look at this

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@binocarlos binocarlos

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@binocarlos @aanm