> The elements of the "authorizations" array are immutable once set. > The server MUST NOT change the contents of the "authorizations" array after > it is created. > If a client observes a change in the contents of the "authorizations" array, > then it SHOULD consider the order invalid.
This is an odd use of "immutable". The other two instances of `immutable` in the document are more traditional. But here, authorizations is returned by a request. Obviously, the response data doesn't change while the client is looking at it. I think what the spec is trying to say is that the conceptual authorizations for a broader transaction shouldn't change. But, I don't think that this quoted paragraph does that. _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
