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

Improve the parsing of folded Xref header fields #230

Open
Julien-Elie opened this issue Feb 20, 2022 · 0 comments
Open

Improve the parsing of folded Xref header fields #230

Julien-Elie opened this issue Feb 20, 2022 · 0 comments
Labels
bug Something isn't working C: general Related to several components P: low Low priority RFC compliance Related to NNTP standards and the format of Usenet articles

Comments

@Julien-Elie
Copy link
Contributor

I once began a patch (for 2.5.x) to handle folded Xref header fields after a bug report, but somehow not finished it.
It could be useful in theory as RFC 5536 allows folding in Xref header fields. Though this is not a common practice, and INN does not generate internally such folded headers.

Also, it enhanced skip_cfws() and skip_fws() to check for a continuation line. It may be the reason why I did not finally commit it (a thorough review of these calls should be done).

I put here what I came up with (for innd, nnrpd, expire, tradspool):

@Julien-Elie Julien-Elie added bug Something isn't working C: general Related to several components P: low Low priority RFC compliance Related to NNTP standards and the format of Usenet articles labels Feb 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working C: general Related to several components P: low Low priority RFC compliance Related to NNTP standards and the format of Usenet articles
Development

No branches or pull requests

1 participant