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
I would like to add some words about having consistency in Request / Response body and their headers.
The goal is to ensure that the headers represents well the body of a message,
Like if there is a Content-Encoding header with a gzip value, then the body should be gzip encoded. And if the client decode the body to make it not gzip he must remove this header. (So a next client in a chain will correctly handle the request)
I have been looking at PSR7 and i see no reference of that, but don't know if this standard should handle this or if we should propose to "amend" PSR7 to add this behavior ?
The text was updated successfully, but these errors were encountered:
I would like to add some words about having consistency in Request / Response body and their headers.
The goal is to ensure that the headers represents well the body of a message,
Like if there is a Content-Encoding header with a gzip value, then the body should be gzip encoded. And if the client decode the body to make it not gzip he must remove this header. (So a next client in a chain will correctly handle the request)
I have been looking at PSR7 and i see no reference of that, but don't know if this standard should handle this or if we should propose to "amend" PSR7 to add this behavior ?
The text was updated successfully, but these errors were encountered: