We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/api/v1/raml provides no Content-Type header (and therefore no encoding). Chrome wrongly assumes windows-1252.
/api/v1/raml
Content-Type
windows-1252
document.charset
document.characterSet
Expected: utf-8 Actual: windows-1252
utf-8
curl http://localhost:8080/api/v1/raml -D - -o /dev/null -s | grep 'Content-Type'
Expected: application/x-yaml; charset=utf-8 or text/yaml; charset=utf-8 Actual: <empty>
application/x-yaml; charset=utf-8
text/yaml; charset=utf-8
The text was updated successfully, but these errors were encountered:
Change Content-Type of /api/v1/raml to application/x-yaml
800220a
Fixes #66
Change Content-Type of /api/v1/raml to application/x-yaml (#105)
c5b8002
No branches or pull requests
Gentics Mesh Version, operating system, or hardware.
Problem
/api/v1/raml
provides noContent-Type
header (and therefore no encoding).Chrome wrongly assumes
windows-1252
.Reproducer
document.charset
ordocument.characterSet
Expected:
utf-8
Actual:
windows-1252
Reproducer 2
curl http://localhost:8080/api/v1/raml -D - -o /dev/null -s | grep 'Content-Type'
Expected:
application/x-yaml; charset=utf-8
ortext/yaml; charset=utf-8
Actual: <empty>
The text was updated successfully, but these errors were encountered: