Skip to content

Option to log header errors #3

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

Closed
jwestbrook opened this issue Apr 27, 2016 · 1 comment
Closed

Option to log header errors #3

jwestbrook opened this issue Apr 27, 2016 · 1 comment

Comments

@jwestbrook
Copy link

On my AWS EC2 instances the apache logs get constantly filled with errors from the ProxyProtocol module because the ELB health checks do not send a ProxyProtocol header with their checks.

ProxyProtocol: no valid header found

Can this log entry be turned into a option so I do not have to turn off all errors? Or possibly point me in the direction to disable them with the current version?

@roadrunner2
Copy link
Owner

roadrunner2 commented Apr 28, 2016

The cleaner way to solve this, IMO, is to have Apache listen on two ports, one with ProxyProtocol enabled, and one without; then configure the ELB to forward requests to the port with ProxyProtocol enabled, but to run the health checks against the other port. Not only does this avoid noise in the log, but it means that the ELB can actually do a proper health check (otherwise the connection just gets aborted, severely limiting the effectiveness of the health check).

Btw., see #2 (comment) for a skeleton of how to do this setup.

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