Problem Details for HTTP APIs
RFC 7807
Yes
No Objection
Note: This ballot was opened for revision 01 and is now closed.
Alvaro Retana No Objection
(Barry Leiba; former steering group member) Yes
(Ben Campbell; former steering group member) Yes
Section 4 talks about how a problem type SHOULD resolve to HTML documentation. Is there ever a case where an API might be standardized to be used by multiple origin servers? Would each server host it's own documentation? Would the problem type be a relative URL under those circumstances? (You say it can be relative, but all the examples are fully qualified) - 4, 2nd paragraph: "New problem types need to carefully consider..." This is a pedantic nit, really a personal pet peeve: Designers of new problem types should consider this. I doubt the types themselves will :-)
(Stephen Farrell; former steering group member) Yes
- 3.1: "SHOULD NOT automatically" de-ref the type URI. Hmm, under what circumstances would it be reasonable for any code to automatically de-ref the type URI? If none, then either s/SHOULD/MUST/ or maybe s/automatically// - 3.1, last para: I'm sure this is a known thing, but I don't know the answer, so I'll ask:-) If I send a request for URL example.com/foo and am re-directed to example.net/bar, against which of those is a relative URL in the problem detail evaluated? I hope the answer is example.net - if not, there could be some attack that could be mounted but I've not got a concrete example to offer. - 3.2, last para: should "media type" be "problem type" at the end? - 4: "typically with the "http" scheme" - your examples are all https, don't you mean https here too?
(Alia Atlas; former steering group member) No Objection
(Alissa Cooper; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Deborah Brungard; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Joel Jaeggli; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Spencer Dawkins; former steering group member) (was Discuss, Yes) No Objection
Thanks for helping me resolve my Discuss.
(Terry Manderson; former steering group member) No Objection