-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
Email payload is broken when set CURLOPT_CRLF = 1 #14165
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
Comments
please tell us a way how we can reproduce this! |
Hi @bagder , |
I can verify that there is a bug with input larger than 64kb. |
When CRLF line end conversion was enabled (--crlf), input after the last newline in the upload buffer was not sent, if the buffer contained a newline. - refs curl#14165
Thank @icing |
I propose #14169 as fix for this, including a modified test case to trigger the bug. If you can build curl yourself it would be nice if you could verify this. (There is a Windows nightly build out there, I think, but could not find a link. Someone can help out here?) |
Daily Windows builds can be found here, scroll down to Artifacts: (don't mind the red, it affects mac runners and pushed a(nother) fix just today.) |
When CRLF line end conversion was enabled (--crlf), input after the last newline in the upload buffer was not sent, if the buffer contained a newline. Reported-by: vuonganh1993 on github Fixes curl#14165 Closes curl#14169
I did this
My program sends emails by curl with CURLOPT_CRLF = 1. Everything worked fine with 7.76.0. Recently, we upgraded to curl 8.8.0 and the email is always broken if the payload is greater than 64Kb. I found out that the payload is missing some data.

To fix the issue, I need to set CURLOPT_CRLF = 0 and add "\r\n" to the end of every line in the payload. it works fine again.
I expected the following
No response
curl/libcurl version
curl 8.8.0
operating system
Windows Enterprise 11
The text was updated successfully, but these errors were encountered: