- From: Willy Tarreau <w@1wt.eu>
- Date: Fri, 26 Sep 2025 05:31:29 +0200
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, masque@ietf.org
Hi Mark, On Fri, Sep 26, 2025 at 09:53:51AM +1000, Mark Nottingham wrote: > Hi everyone, > > With my HTTP Proxy Error Types Expert hat on, we've received the following > request, and per the RFC I'm asking for any community feedback. > > Thoughts? It's unclear to me what this corresponds to. Is this someone asking what status code to use for a protocol extension, in their code, someone disagreeing with established status codes, or anything else ? FWIW in haproxy when we reject accesses (based on ACL or anything else), we also use 403. I don't know if this helps. > > Begin forwarded message: > > > > > > Type of Assignment: > > Name: origin_acl > > Description: The intermediary rejected the HTTP request based on ACL rules which prohibit access to the requested next hop. > > Extra Parameters: None > > Recommended HTTP Status Code: 403 > > Response Only Generated by Intermediaries: true > > > > Registry: > > https://www.iana.org/assignments/http-proxy-status/http-proxy-status.xhtml#http-proxy-error-types > > > > Description: > > We're running a MASQUE/CONNECT/ProxyB server for (multi party) private relay style architectures and would like to signal to clients that a proxy attempt was rejected due to origin ACL rules. > > > > Additional Info: > > https://www.rfc-editor.org/rfc/rfc9209.html#name-proxy-error-types > > -- > Mark Nottingham https://www.mnot.net/ Regards, Willy
Received on Friday, 26 September 2025 03:31:35 UTC