Hi Pawel, On Tue, 7 Jul 2026, at 16:01, Pawel Kowalik wrote: > > [snip] > > PS. I am not a big fan of off-list discussion when the issue was brought > up to the list. This is an adopted document.
You're right, so I should explain our rationale, and the WG can decide if we made the right choice. Section 4.6 of RFC 9205 provides guidance to on how specifications should use HTTP status codes, and advises against being excessively specific about which status codes to use, due to the fact that they are often generated by components other than the application itself. Given that, 409 seems definitely wrong, so we decided to revert it. Remember it was not itself the outcome of a WG discussion. To resolve the question about the status code in this scenario, I propose the following change: OLD: Redirect requests for searches, where more than one object is returned, and help queries, as described by [RFC9083], are not supported. Servers MUST return an HTTP 409 for these requests. NEW: Redirect requests for searches, where more than one object is returned, and help queries, as described by [RFC9083], are not supported. Servers MUST return a 4xx status for these requests. This would 400, 404, or similar, and is in keeping with the guidance in RFC 9205. Let me know what you think. G. _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
