[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: |
Wed, 26 Jun 2024 13:30:03 -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):
> I'm using a string port because the server wants that content as a
"file" object (in a multipart/form-data body), and the file: argument of
the writer alist interprets a string as a filename.
Hm, that's unfortunate - the body being multipart shouldn't really make a
difference, normally. Maybe a way to force that, even if all the entries
are strings would be helpful as well...
--
Ticket URL: <https://bugs.call-cc.org/ticket/1838#comment:10>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
- Re: #1838: http-client does not multipart encode string ports properly, (continued)
- 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
- 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 <=
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/28
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/28
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/28
- Re: #1838: http-client does not multipart encode string ports properly, Chicken Trac, 2024/06/28