Its not really an issue of elegance. Either way is not pleasing, but given that your code is the only consumer of the exposed http.Send, my recommendation is that you isolate your end users from the Go.http's evolution by including the (dup) code in your source and removing it when the update release fixes the issue. Transition would be transparent to your end users.