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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: