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.

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

Is a prohibition against mixed line termination a requirement? #703

Closed
martinthomson opened this issue Jan 29, 2021 · 1 comment · Fixed by #767
Closed

Is a prohibition against mixed line termination a requirement? #703

martinthomson opened this issue Jan 29, 2021 · 1 comment · Fixed by #767

Comments

@martinthomson
Copy link
Contributor

This text implies a requirement:

HTTP allows the transfer of text media with plain CR or LF alone representing a line break, when such line breaks are consistent for an entire representation.

I would have said instead that HTTP itself doesn't care whether content adheres to this stricture, though some implementations could (or MAY) normalize line endings before sending or after receiving content that uses a text media type.

@reschke
Copy link
Contributor

reschke commented Feb 2, 2021

Maybe we can improve the spec by just killing the whole subsection? It refers to the canonical form in MIME, then say we don't neef that, and then makes recommendations for text/* that AFAIU everbody ignores.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants