mikesimons / pacyak Goto Github PK

Readly was a 20 minute hacky half arsed attempt at what go-getter does properly.

You get the golang error messages for some types of failure. DNS lookup failures are one of them IIRC (with an err containing getsockopt that I can't reproduce atm due to an upstream proxy)

As per title

It's a bit more featured than we need and I suspect it may be dropping some connections on the floor.
The only use cases we need are accepting HTTP requests, CONNECT requests, establishing a connection with and copying the request to the target & copying the response back from the target.

It would be handy to know when pacyak has flipped to the direct handler.

After the proxy has been running a while it can have quite a few sockets open.

This is most likely an issue with go-proxy. The HTTP RFC states that connections may be closed at any time and that clients or servers should deal with it.

If there is no obvious cause for a socket leak then it'd make sense to track usage of connections and shut them down after a period of inactivity.

Very nice idea and definitely something I would use if I can make it work ...
For some reason all I am getting is

./pacyak  http://proxyconf/proxy.pac  --log-level debug
INFO[0001] PAC availability check                        available=true
INFO[0001] PAC availability check passed; switching from direct
ERRO[0008] Sandbox error!                                response= sandbox_error="ReferenceError: 'myIpAddress' is not defined" url="http://www.google.com/"
ERRO[0023] Error performing roundtrip                    error="dial tcp 172.217.22.164:80: i/o timeout"