Excellent call, my friend. Apparently, `NextPart()` invalidates the previous parts.
On Fri, Dec 8, 2017 at 6:01 PM, Dave Cheney <d...@cheney.net> wrote: > Perhaps calling next part is consuming reader, so when you break at once > you hit io.EOF, the reader you memorised has been consumed. > > Again, just a guess, I’ve never used the multipart package in anger. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/golang-nuts/XoSPHwWfyQ8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
