fix redirection of async endpoints response codes from "202 - Accepted" to "303 - See other"
Bug #1538653 reported by
milan k
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Opinion
|
Wishlist
|
Unassigned |
Bug Description
Currently, there are /v1/controllers
According to the RFC[1][2], this shouldn't be the case unless a resource was created by the original request.
Please correct this to a "303 - See Other"[3] response code or avoid using the location header.
It seems the endpoints affected are (in terms of source code):
ironic/
NodeConsoleCon
NodeStatesCont
NodeStatesCont
[1] https:/
[2] https:/
[3] https:/
To post a comment you must log in.
That's pretty arguable (as I already mentioned offline), as there seems to be enough places even in RFC's where 202+location are used. Also 202 requires some reference to actual results, which seems a perfect use case for the location header to me. Anyway, pleae feel free to bring this question to a wider discussion on the ML or the team meeting.