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):

 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. The "procedure that
 returns a string port" solution is working for me for now -- another
 possible solution is to have the implicit redirect behavior be optional
 (maybe automatic if the writer argument or one of it's leaves is or isn't
 a port), and allow the user to set up another request for the redirected
 URI.

 Thank you so much for being so responsive, and for this great library!

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