- changed status to open
Content-type header in HTTP response from resource server
Issue #107
resolved
There may be some cases where resource server would like to specify other Content-Type value than "application/json" e.g. providing RFC 7807 compliant Problem Details which defines "application/problem+json" content-type. It would be appropriate to modify the relevant clause of 6.2.1 Protected resources provisions as follows;
- shall send the Content-type HTTP header Content-Type: application/json; charset=UTF-8 if applicable;
Comments (7)
-
-
- changed status to resolved
-
- changed component to Part 1: Baseline
-
- changed component to FAPI 1 - Part 1: Baseline
-
- changed component to FAPI 1 – Part 1: Baseline
-
- changed component to FAPI 1 – Baseline
-
- changed component to FAPI 1: Baseline
- Log in to comment
Noted. Please provide the specific text modification proposal and if possible, a pull request.