-
Notifications
You must be signed in to change notification settings - Fork 284
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
0.7.24: exception "Header is missing ':'" #1220
Comments
I've tested with the uploaded example and that still seems to work. The only change in that area seems to be #1183, but it isn't obvious how that would result in this kind of error. Which way do you generate the client request? |
I actually never saw client code. But I know that colleagues use retrofit. Here, I extracted headers along with some data from client logs:
|
shouldn't there be a carriage-return and line-break after the HTTP headers? (after content-length) would also end with another set of line-break and carriage-return and a
|
It might be it got eaten up by logging facility. square/retrofit#650 |
Hm. Actually, this request should consist of 5 values. File and some other data. But log doesn't have it. And boundary string appears only 2 times (in part mentioned above). |
Can you capture this through wireshark instead? |
Unfortunately, I can't do it right now. Here's full logs (server and client, both): https://gist.github.com/sigod/524683e707f5efb9f416 logInfo("ln: %s", ln); // added this line to see what kills request
enforce(colonpos > 0 && colonpos < ln.length-1, "Header is missing ':'."); |
I isolated changes from #1101. And now this requests works. |
Yes it looks like the issue is with this line: https://github.com/rejectedsoftware/vibe.d/blob/master/source/vibe/inet/webform.d#L140 It expects |
Good! |
Checked
Saved file size: 368606 |
Isn't the issue just that the |
Yes, I'm sure in it. |
Always skip the boundary when parsing a multi-part form part. Fixes #1220.
This exception happens in 0.7.24 when we make multipart request:
0.7.23 works flawlessly.
The text was updated successfully, but these errors were encountered: