The plot thickens. My attempt to make a minimally-reproducible short example has failed - my demo (here <https://play.golang.org/p/wQMBLKY0R0>) does not reproduce the problem, even though it's mostly copy paste. That leaves the code in my original project to blame.
The server-being proxied is simply: *python -m SimpleHTTPServer* Any recommendations for instrumenting my code to find the bottleneck? I'm going to have a quick look for idioms (IIRC Dave Cheney mentioned something about a talk he did in europe about HTTPTrace?), otherwise I'm going to scatter logging of the current ms. On Wednesday, 16 November 2016 16:01:50 UTC+11, Tom wrote: > > Hi guys, > > I've been working on a HTTP reverse proxy that has an auth/authorization > function. It all works well, however I have noticed significant additional > latency - and I cannot work out why. From what I can tell, me hitting my > service from chrome on localhost should work just fine - I have a very > beefy machine! (8core 3.4Ghz Amd64) > > Anyone have any insights into httputil.ReverseProxy, or have any ideas > where to begin? > > The method is here: > https://github.com/twitchyliquid64/pushtart/blob/master/src/pushtart/webproxy/handler.go#L61 > > Cheers, > Tom > -- 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.
