I suspect this has to do with the fact that you're doing a roundtrip for
its side effects, but not reading the response body or closing it. If I fix
that, everything seems to work as expected.
Try configuring the TLS client with t.TLSClientConfig =
&tls.Config{InsecureSkipVerify: true}
On Mon, 19 Nov 2018 at 20:30, <grego...@unity3d.com> wrote:
> Hi folks!
>
> Hoping somebody can help me figure out what I'm doing wrong (or what Go's
> doing wrong in the small chance it's that).
>
> It _seems_ Go's reverse proxy doesn't support 100 Continue when the
> backend is HTTP/2 (but I'm guessing).
>
> I put up the sample at https://github.com/gholt/proxrepro -- just `go run
> main.go` and then look at the `trace` file that's output.
>
> You can see where curl sends its request headers with the Expect:
> 100-continue but the first thing it gets back is 200 OK and then
> "weirdness" ensues.
>
> -- Greg Holt
>
> --
> 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.
>
--
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.
