fix(HTTP): error boundary in HTTP-Header, Content-Type#4953
fix(HTTP): error boundary in HTTP-Header, Content-Type#4953HR1025 wants to merge 1 commit intopocoproject:mainfrom
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? |
|
Replaced by #5100 |



see
https://www.rfc-editor.org/rfc/rfc2046#section-5.1Poco carries extra ''", which can cause nginx to return 'Malformed multipart message', upload fail.