goproxy
goproxy copied to clipboard
elazarl
An HTTP proxy library for Go
I'd to access the proxy address that was used by the client to connect to the proxy and forward it as a request header. For example, if I have a...
First of all great job. I love goproxy! I came across a bug after i managed to get MITM and HTTPS hijacks working. It seem's like some requests are parsed...
Client error： 2019/06/06 10:18:34 session[6] created 2019/06/06 10:18:34 200 stream 21b94610319abbb2f4f104630315447b created 2019/06/06 10:19:14 [ERR] yamux: keepalive failed: i/o deadline reached 2019/06/06 10:19:14 [ERR] yamux: Failed to read header: broken...
```bash GOOS=linux GOARCH=mipsle ``` can't proxy https when run on router, the http proxy is ok
@elazarl wanted to know what your plan was.. I've seen quite a bit of traction in my fork.. with the radically changed API.. I remember you telling me you'd like...
Hi, I used for a test project (https://github.com/elazarl/goproxy/tree/master/examples/goproxy-customca). I used the function `proxy.OnRequest().DoFunc(` to log the RequestURI and it's working as expected. Whereas, on function `proxy.OnResponse().DoFunc(` when I try to...
+ go test -compiler gc -ldflags '-X github.com/elazarl/goproxy/version.GitSHA=a96fa3a318260eab29abaf32f7128c9eb07fb073 -extldflags '\''-Wl,-z,relro '\''' --- FAIL: TestNoProxyHeaders (0.00s) proxy_test.go:535: Got Connection header from goproxy map[User-Agent:[Go-http-client/1.1] Connection:[close] Accept-Encoding:[gzip]] --- FAIL: TestNoProxyHeadersHttps (0.04s) proxy_test.go:535: Got...
``` panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x0 pc=0x4633f6] goroutine 69 [running]: panic(0x771260, 0xc82000a130) /usr/lib/go/src/runtime/panic.go:464 +0x3e6 log.(*Logger).Output(0x0, 0x2, 0xc8204d2370, 0xad, 0x0, 0x0) /usr/lib/go/src/log/log.go:147...
The library [relies on `http.Hijacker`](https://github.com/elazarl/goproxy/blob/master/https.go#L70) to do CONNECT. According to https://golang.org/pkg/net/http/#Hijacker the interface isn't implemented by HTTP/2 connections (by design) and as such this isn't supported by this library. See...
I've noticed it's about 5 times slower to retrieve https addresses when chaining proxies (using another proxy on internal http calls) when compared to chained proxy http calls. The relevant...
