[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-09-04 Thread Ned Deily
Change by Ned Deily : -- nosy: +barry, maxking, r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-09-03 Thread tzickel
tzickel added the comment: It should be noted that this causes a big headache for users of requests / urllib3 / etc... as those print on each multipart response a logging warning based on this bug, and it might cause people to go try debugging valid code:

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-03-11 Thread Christian Schmidbauer
Christian Schmidbauer added the comment: @martin.panter: I see a relation to issue 29353, but I don't see why this report here is a duplicate. Could you elaborate on this? Issue 29991 contains parts of what I reported here, but it is closed "resolved" and refers back to 29353. I also tried

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-03-07 Thread Martin Panter
Martin Panter added the comment: Probably the same as Issue 29353. I remember than enabling "headersonly" can create inconsistencies in the message object. But I don't remember the details. According to Issue 29991 (another duplicate), my patch for Issue 24363 might help. But I don't think

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-03-07 Thread Christian Schmidbauer
Christian Schmidbauer added the comment: Apologies, here are the correct commit IDs: https://github.com/python/cpython/commit/89285439c7f94a3e62cee3d15e343218903c2af8 https://github.com/python/cpython/pull/12214/commits/a82e662ab3339072d7b86a8090989fba60ef9c37 --

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-03-07 Thread Roundup Robot
Change by Roundup Robot : -- keywords: +patch pull_requests: +12204 stage: -> patch review ___ Python tracker ___ ___

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-03-07 Thread Christian Schmidbauer
Change by Christian Schmidbauer : -- hgrepos: +381 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36226] multipart/related header causes false positive StartBoundaryNotFoundDefect and MultipartInvariantViolationDefect

2019-03-07 Thread Christian Schmidbauer
New submission from Christian Schmidbauer : The current implementation of `multipart/related` in urllib triggers header defects even though the headers are valid: `[StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()]` The example header is valid according to RFC 2387