Skip to content

Conversation

@sjohnsonaz
Copy link

I added a small bit of error handling to the proxy section. It causes the server to return a 503 status, rather than exit.

@apixandru
Copy link

apixandru commented Jan 30, 2018

I'm having this exact same problem now, the server just crashes with regular chrome usage.
If the http server proxies /request1 to http://otherserver/request and i go and access /request1 and refresh a couple of times without letting the request go through, the http-server crashes because the proxy crashes.

@rafaelsales
Copy link

It feels like the owner has to add more maintainers to the project so that it scales, or it will become a ghost town

@BigBlueHat
Copy link
Member

This generally looks good. It needs some tests and the whitespace changes removed. Once those are added, this seems like a good addition. Thanks!

@thornjad
Copy link
Member

Closing in favor of the non-crashing logging in #477

@thornjad thornjad closed this Apr 15, 2019
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.

5 participants