You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone,
it would be great if there was http3/quick support in the future. It would also be great if you could configure the used/allowed ciphers.
I think it would be good to be able to configure this generally.
In the future, however, it would also be practical to be able to configure this for each asset. There may be services that don't support TLS 1.3, for example, but the rest should use TLS 1.3 exclusively, and so on. I'm thinking of something similar to the ACL groups, but only for HTTP version, ciphers, and TLS, which can be assigned to each proxy service/stream. What does the community think? Would you also like to see something like this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
it would be great if there was http3/quick support in the future. It would also be great if you could configure the used/allowed ciphers.
I think it would be good to be able to configure this generally.
In the future, however, it would also be practical to be able to configure this for each asset. There may be services that don't support TLS 1.3, for example, but the rest should use TLS 1.3 exclusively, and so on. I'm thinking of something similar to the ACL groups, but only for HTTP version, ciphers, and TLS, which can be assigned to each proxy service/stream. What does the community think? Would you also like to see something like this?
Best regards, sit
Beta Was this translation helpful? Give feedback.
All reactions