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

Add correction about TCP_TLS routers in docs #10489

Closed
wants to merge 169 commits into from

Conversation

shivanipawar00
Copy link
Contributor

What does this PR do?

Resolves #10186
Adds the correction on TCP-TLS routers

More

  • Added/updated documentation

rtribotte and others added 30 commits September 19, 2022 13:52
Co-authored-by: Mathieu Lonjaret <mathieu.lonjaret@gmail.com>
Co-authored-by: Kevin Pollet <pollet.kevin@gmail.com>
Co-authored-by: Mathieu Lonjaret <mathieu.lonjaret@gmail.com>
Co-authored-by: Tom Moulard <tom.moulard@traefik.io>
Co-authored-by: Romain <rtribotte@users.noreply.github.com>
Co-authored-by: Kevin Pollet <pollet.kevin@gmail.com>
Co-authored-by: Kevin Pollet <pollet.kevin@gmail.com>
Co-authored-by: Michael Kuhnt <michael.kuhnt@daimler.com>
Co-authored-by: Julien Salleyron <julien@containo.us>
Co-authored-by: Mathieu Lonjaret <mathieu.lonjaret@gmail.com>
@ldez ldez changed the title Add correction about TCP_TLS routers in docs #10186 Add correction about TCP_TLS routers in docs Mar 2, 2024
Copy link
Member

@rtribotte rtribotte left a comment

Choose a reason for hiding this comment

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

Hello @shivanipawar00,

Thanks for opening this PR!

I have a few review comments.
Also, as a bug fix, this PR should target the v2.11 branch, could you please rebase the changes on it?

@@ -870,7 +870,8 @@ The [supported `provider` table](../../https/acme.md#providers) indicates if the

### General

If both HTTP routers and TCP routers listen to the same EntryPoint, the TCP routers will apply *before* the HTTP routers.
In case of non-TLS Entrypoint, both HTTP routers and TCP routers listen to the same EntryPoint, the TCP routers will apply *before* the HTTP routers.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
In case of non-TLS Entrypoint, both HTTP routers and TCP routers listen to the same EntryPoint, the TCP routers will apply *before* the HTTP routers.
For non-TLS connections, if HTTP and TCP routers listen on the same EntryPoint, the TCP routers will apply *before* the HTTP routers.

@@ -870,7 +870,8 @@ The [supported `provider` table](../../https/acme.md#providers) indicates if the

### General

If both HTTP routers and TCP routers listen to the same EntryPoint, the TCP routers will apply *before* the HTTP routers.
In case of non-TLS Entrypoint, both HTTP routers and TCP routers listen to the same EntryPoint, the TCP routers will apply *before* the HTTP routers.
In case of TLS Entrpoint, both HTTPS and TCP-TLS routers listen to the same EntryPoint, the HTTPS routers will apply *before* the TCP-TLS routers.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
In case of TLS Entrpoint, both HTTPS and TCP-TLS routers listen to the same EntryPoint, the HTTPS routers will apply *before* the TCP-TLS routers.
For TLS connections, if HTTPS and TCP-TLS routers listen on the same EntryPoint, the HTTPS routers will apply *before* the TCP-TLS routers.

@shivanipawar00
Copy link
Contributor Author

Shifting all changes of the PR to #10510 due to too many merge conflicts caused by the rebase

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

Successfully merging this pull request may close these issues.

Improve documentation in regards to TCP-TLS and HTTPS routing priorities