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

How to correctly close access to default backend in haproxy #676

Open
fo511 opened this issue Sep 6, 2024 · 3 comments
Open

How to correctly close access to default backend in haproxy #676

fo511 opened this issue Sep 6, 2024 · 3 comments
Labels

Comments

@fo511
Copy link

fo511 commented Sep 6, 2024

Hello.
My haproxy ingress is published in internet.
For services and ingresses that are explicitly defined I'm able to limit access by IP/request path etc...
But default backend is opened without limitation.
So everyone can just query my IP without hostname and request non-existennt files or try to test exploits.
I tried to add strict_sni option to global object like that

    runtime_apis: 
      - strict_sni: true
        address: "0.0.0.0:8443"
        name: https

I expect that option will be added to default https frontend actually it was added to stats frontend.
I also cannot find a way to add backend-config-snippet to default backend so I would be able to define custon deny rules inside.

So question is how to correcly protect default backend from unlegitimate requests?

Copy link

stale bot commented Oct 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 17, 2024
@oktalz oktalz removed the stale label Oct 23, 2024
Copy link

stale bot commented Nov 23, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 23, 2024
@oktalz oktalz removed the stale label Dec 4, 2024
Copy link

stale bot commented Jan 4, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants