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

A way that allows active closing of connections, similar to the 444 status code in nginx #10898

Open
2 tasks done
AtarisMio opened this issue Jul 12, 2024 · 2 comments
Open
2 tasks done

Comments

@AtarisMio
Copy link

AtarisMio commented Jul 12, 2024

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?

I have looked into related issue, where a proposal was mentioned. However, this proposal only allows for closing connection passive. It controls the closing of connections through timeouts or max connections, whereas the 444 status code in nginx can be controlled by the upstream.

@nmengin
Copy link
Contributor

nmengin commented Jul 15, 2024

Hello @AtarisMio,

Discussing the issue with other maintainers, we're unsure to clearly understand your need.
Could you describe your use-case more elaborately, please?

@aless3
Copy link

aless3 commented Jul 18, 2024

I think what they are trying to achieve is closing the connection without a response

the use case (at least for me) would not return any response if a scanner tries to connect to subdomain "random.domain.tld", like when you connect to https://paudg.box/ (random domain i just typed that doesn't exist)

with logging etc this would allow banning anyone trying to find which services are present (like when using wildcard certificates I think)

useful to preemptively ban generic subdomain scanning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants