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

Registration Request: destination_protocol_prohibited #2

Open
vparla opened this issue Dec 15, 2022 · 1 comment
Open

Registration Request: destination_protocol_prohibited #2

vparla opened this issue Dec 15, 2022 · 1 comment
Labels
new registration A request for registering a new link relation type

Comments

@vparla
Copy link

vparla commented Dec 15, 2022

Name

destination_protocol_prohibited

Description

The intermediary is configured to prohibit connections to the protocol on the next-hop

Extra Parameters

The textual name of the protocol, such as as “udp”, “tcp”, “quic”, “http”, etc.

Recommended HTTP Status Code

403

Response Only Generated by Intermediaries

This proxy error type can only be generated by an intermediary

Reference

No response

Additional Information

Proxy requests can transport many protocols including lower level TCP, UDP and higher level protocols such as QUIC or HTTP and different encryption mechanisms when chaining Proxy requests together.
A Proxy may want to reject a protocol for a variety of reasons.
For example, a Proxy may reject TCP to host foo.com, but allow UDP to host foo.com based on some policies.
Having a way to express that to clients would be ideal.

We have plans to implement this code in our proxies, and would prefer it be standardized so 3rd parties can interoperate with us.

@vparla vparla added the new registration A request for registering a new link relation type label Dec 15, 2022
@vparla
Copy link
Author

vparla commented Feb 29, 2024

any status on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new registration A request for registering a new link relation type
Development

No branches or pull requests

1 participant