Files
Maor LegerandGitHub 947613eac0 [core] RLC content-type header fix (#32672)
### Packages impacted by this PR

@azure-rest/core-client

### Issues associated with this PR

Resolves #31843

### Describe the problem that is addressed by this PR

Per the HTTP spec, `application/json` content type does not define a
charset as all JSON is UTF and @azure/core-client uses `application/json` for its
default content-type for JSON.

In migrating KeyVault to modular, based on RLC, we noticed that the
default content type in @azure-rest/core-client uses `application/json;
charset=UTF-8`

While compliant servers _should_ accept this version and ignore the
charset, in practice KeyVault rejects requests to certain endpoints with an
unsupported content type.

Since the charset parameter is not needed and not defined per spec,
removing it will increase compatibility. 

See:

- https://www.iana.org/assignments/media-types/application/json
- https://datatracker.ietf.org/doc/html/rfc4627#section-6


Finally, looking at other languages shows that others define the
content-type as `application/json` by default, without the charset.
2025-01-24 08:31:14 -08:00

7 lines
194 B
JSON

{
"AssetsRepo": "Azure/azure-sdk-assets",
"AssetsRepoPrefixPath": "js",
"TagPrefix": "js/devcenter/developer-devcenter-rest",
"Tag": "js/devcenter/developer-devcenter-rest_13eff72e03"
}