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

remove separate tls listen for haproxy #543

Merged
merged 2 commits into from
Dec 18, 2024
Merged

remove separate tls listen for haproxy #543

merged 2 commits into from
Dec 18, 2024

Conversation

ewdurbin
Copy link
Member

haproxy has natively supported http/2 for a long time.

This listen (combined frontend/backend) was added long ago before haproxy supported http/2 (back when it was called spdy).

Drop the http server config for http/2, and move all binds back into the main frontend.

haproxy has natively supported http/2 for a _long_ time.

This listen (combined frontend/backend) was added long ago before haproxy supported http/2 (back when it was called spdy).

Drop the http server config for http/2, and move all binds back into the main frontend.
@ewdurbin
Copy link
Member Author

basically a long overdue revert of 794c3cc

Copy link
Member

@JacobCoffee JacobCoffee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ssl_fc function returns true if the connection came in over HTTPS neat

@ewdurbin ewdurbin merged commit f5d76ee into main Dec 18, 2024
2 checks passed
@ewdurbin ewdurbin deleted the rm_tls_listen branch December 18, 2024 20:01
ewdurbin added a commit that referenced this pull request Dec 18, 2024
This condition was in place to support the proxy nonsense we had going that was removed in #543, we can go ahead and always set this now that our frontend is handling tls
ewdurbin added a commit that referenced this pull request Dec 18, 2024
This condition was in place to support the proxy nonsense we had going that was removed in #543, we can go ahead and always set this now that our frontend is handling tls
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.

2 participants