[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: #1838: http-client does not multipart encode string ports properly
From: |
Chicken Trac |
Subject: |
Re: #1838: http-client does not multipart encode string ports properly |
Date: |
Tue, 25 Jun 2024 06:57:13 -0000 |
#1838: http-client does not multipart encode string ports properly
-------------------------------------------+------------------------------
Reporter: Woodrow E Douglass | Owner: (none)
Type: defect | Status: new
Priority: major | Milestone: someday
Component: unknown | Version: 5.3.0
Resolution: | Keywords: http http-client
Estimated difficulty: |
-------------------------------------------+------------------------------
Comment (by sjamaan):
Hi Woodrow,
Thanks for the bug report and the patch!
As far as I can see, the code specifically contains a case for the string
port, there's even a procedure called {{maybe-string-port-length}} which
obtains the string's length. So the port shouldn't be closed before it
tries to read.
There's also a {{test-group}} in the test suite named {{"alist form data
body with string port"}} which is supposed to test this particular case,
but of course I wouldn't rule out any bugs. Perhaps you can have a look at
that and see how it differs from your use case?
If you are sure it's a bug, I'd appreciate a self-contained sample (or
better yet, a failing test case as a patch to the test suite) which fails.
--
Ticket URL: <https://bugs.call-cc.org/ticket/1838#comment:1>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
- #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/24
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/24
- Re: #1838: http-client does not multipart encode string ports properly,
Chicken Trac <=
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/25
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/25
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/25
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/25
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/25
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/25
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/26
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/26
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/26
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/26