[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: |
Fri, 28 Jun 2024 07:13:49 -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):
> Hmm it seems (max-redirect-depth 0) means unlimited, back to the
drawing board
No, that should indeed stop redirects altogether. Using `(max-redirect-
depth #f)` disables it. The docs state this pretty clearly, and the code
definitely checks for this.
Anyway, I just pushed a few commits to master, could you check it out if
this makes it easier for you? See https://code.more-magic.net/http-client
(you can clone it with `git clone https://code.more-magic.net/http-
client`, change into the dir and type `chicken-install` to install it)
This new version changes two things:
- It is possible to use `data:` with a string instead of `file:` and a
port to force a multipart request even with static strings.
- It detects whether ports passed in via `file:` are already closed and
raises a specific exception `(exn http port-already-consumed)` with some
hints as how to fix it.
--
Ticket URL: <https://bugs.call-cc.org/ticket/1838#comment:11>
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/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, 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