-
Notifications
You must be signed in to change notification settings - Fork 2.3k
fix(HTTP): error boundary in HTTP-Header, Content-Type #4953
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
base: main
Are you sure you want to change the base?
Conversation
@HR1025 , can you please correct unit tests to match the code, please? |
see `https://www.rfc-editor.org/rfc/rfc2046#section-5.1` Poco carries extra ''", which can cause nginx to return 'Malformed multipart message', upload fail.
Of course. The test cases have been corrected |
The way Poco handles this might be correct and compliant with the standard (by adding "). According to the compatibility description in RFC 2046, when the boundary contains special characters, it is necessary to add ". The relevant description is as follows:
However, Poco's generated boundary does not include any special characters, so removing the " would cause no harm. |
@HR1025 Does this mean that problem is not in Poco at all because it follows the RFC. |
|
https://github.com/fdintino/nginx-upload-module/blob/master/ngx_http_upload_module.c
|
@HR1025, I assume that there is nothing to be done in Poco for this matter, right? |
see
https://www.rfc-editor.org/rfc/rfc2046#section-5.1
Poco carries extra ''", which can cause nginx to return 'Malformed multipart message', upload fail.