Using #90's behavior for IO.copy_stream seems fine for HTTP now.
Now the problem is that even if the IO object is properly exposed so that it does not raise an exception, copying IO to an SSLSocket as a destination causes a browser error. I will troubleshoot this further, but so far it seems to always happen.
One of the #90 twins.
Using #90's behavior for
IO.copy_stream
seems fine for HTTP now.Now the problem is that even if the IO object is properly exposed so that it does not raise an exception, copying IO to an SSLSocket as a destination causes a browser error. I will troubleshoot this further, but so far it seems to always happen.
Will work on repro for this also.