Re: #1838: http-client does not multipart encode string ports properly

[Chicken Trac]

#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 Woodrow E Douglass):

 So the test case works, and i think that test is valuable, but I've found
 an interesting thing:

 The request in question is a PUT request against a PULP object server
 https://pulpproject.org/

 The same request that fails with
 {{{
 Error: (read-string!) port already closed: #<input port "(string)">
 }}}
 against the pulp server, succeeds when put against posttestserver.dev
 (which also has ssl enabled, so ssl is ruled out as a cause here)

 I'll keep investigating, i'm not sure what the issue is yet. Sorry for the
 noise, this issue is more nuanced then i originally thought

-- 
Ticket URL: <https://bugs.call-cc.org/ticket/1838#comment:2>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.