Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Clarify use of byte-order mark (BOM) in text/plain responses #325

Open
ralfhandl opened this issue Mar 20, 2024 · 0 comments · May be fixed by #2017
Open

Clarify use of byte-order mark (BOM) in text/plain responses #325

ralfhandl opened this issue Mar 20, 2024 · 0 comments · May be fixed by #2017
Assignees
@Hubert-Heijkers
Labels
JSON Format JSON Format Protocol Protocol, URL Conventions V4.02

Comments

@ralfhandl
Copy link
Contributor

The specification is currently unclear on the use of byte-order marks in "plain text" responses to e.g. /$count segments or /$value requests to numeric properties.

Proposal

OData services REALLY SHOULD NOT send a byte-order mark in responses with Content-Type: text/plain.

Clients SHOULD be aware that it is returned by some services.

Imported from ODATA-1426
@ralfhandl ralfhandl added JSON Format JSON Format Protocol Protocol, URL Conventions Resolved labels Mar 20, 2024
@ralfhandl ralfhandl linked a pull request Oct 24, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Hubert-Heijkers Hubert-Heijkers

Labels
JSON Format JSON Format Protocol Protocol, URL Conventions V4.02
Projects
OData TC
Status: Review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

325 byte order mark in text/plain oasis-tcs/odata-specs
2 participants
@ralfhandl @Hubert-Heijkers