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

 Thanks for the investigation and test case, that makes more sense now.
 I'll look into it, hopefully within the next two weeks.

 From a quick glance, I think the code for closing ports needs to be
 overhauled - I think we need to rewind the port position. I'm not sure
 what to do with custom ports in this case though! They don't have a seek
 operation defined on them.

 One option would be to store the body somewhere (in memory, or on disk?
 What if it's an infinite stream?) and resubmit it, but that seems rather
 ugly. I'd also have to see how other HTTP libraries deal with this
 eventuality.

 As an immediate workaround, you could simply change the URL in your
 application to use the final URL after redirection, to avoid getting
 redirected in the first place. This of course only works if the redirect
 is stable and predictable.

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