-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
long lines #683
Comments
@ericfaurot is working on a new headers and message parser which will make it easier to handle long lines correctly. to be followed... |
i just got bitten by some long lines other people were sending. who do i bribe for progress on this? |
No bribing required, it' s taking time because it has a few tentacles and requires rewriting some tricky code... but it's almost done for real. |
I'm preparing a quick fix to workaround and commit on Sunday. |
we've bumped considerably the line limit, this should fix user issues but itś not the proper way to fix it which is still being worked on. |
@ericfaurot has committed a new message parser which can process long lines and which makes it possible to solve this ticket for good. He is currently investigating if there are other areas that still work with long lines but we think there aren't and this ticket might be closed soon. |
a diff is pending review by @ericfaurot to bump the maximum line size to 64k which is the limit imposed in lower level subsystems and which is a reasonnable high bound. |
committed, so long nuisance. |
long lines have been a constant issue for users.
on one side, RFC provides SHOULD and MUST to determine what is an acceptable line size, on another hand being too strict with this has proved to break communications frequently.
we need to reassess how we're handling them.
The text was updated successfully, but these errors were encountered: