You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Figure 16 the server answers an unsuccessful request with 422 and includes a Link header stating which profiles it can handle for the selected resource. The text explaining the figure does not mention this link header which leaves its nature unclear.
Suggestion (to be added between "... the resource at hand." and "Such a response ...":
(If we decide to use Request Content Negotiation Style as proposed in #38, the profile would go in a Accept-Profile heading and the text be changed accordingly).
The text was updated successfully, but these errors were encountered:
In Figure 16 the server answers an unsuccessful request with
422
and includes aLink
header stating which profiles it can handle for the selected resource. The text explaining the figure does not mention this link header which leaves its nature unclear.Suggestion (to be added between "... the resource at hand." and "Such a response ...":
(If we decide to use Request Content Negotiation Style as proposed in #38, the profile would go in a
Accept-Profile
heading and the text be changed accordingly).The text was updated successfully, but these errors were encountered: