rosahaj
rosahaj
> @axelrindle Thank you. > > FYI, `ConnectDialWithReq` function solved my problem. Could you please provide an example for how you used `ConnectDialWithReq`? I'm also stuck on this.
> Here you go @rosahaj > > ```go > proxyServer.ConnectDialWithReq = func(req *http.Request, network, addr string) (net.Conn, error) { > if strings.Contains(req.URL.Path, "somethingyouwant") { > return proxyServer.NewConnectDialToProxyWithHandler("http://proxy1.com", func(req *http.Request) {...
@chekun Unfortunately setting `Tr.Proxy` doesn't ensure the request goes through the returned proxy URL: ```go package main import ( "fmt" "log" "net/http" "net/url" "regexp" "strings" "github.com/elazarl/goproxy" ) func logOnNewConnection(proxyName string)...
I have tried using the new `-upstream` parameter, but the connection isn't being tunneled through the specified socks proxy. I believe the issue is that CustomDialer is initialized in the...
> Amazing! Few questions please: > > 1. Does it support proxy authentication in the form of user:pass@proxy_address:port ? > > 2. Can I set a different proxy per request...
> @LyleMi I'm currently testing the tlsproxy project. I noticed that it is based on the https://github.com/bogdanfinn/tls-client project for customizing the ja3 fingerprints. Do you know how is that library...
> @LyleMi I'm currently testing the tlsproxy project. I noticed that it is based on the https://github.com/bogdanfinn/tls-client project for customizing the ja3 fingerprints. Do you know how is that library...
@OddSquirrel Try chaning` ` to `` (adding a `/` prefix to the `src` attribute). The script likely cannot be found because you're using a relative path.
> Okay, I now see that this is not happening on much lower versions in this tool like Chrome 70. Based on some quick research, it seems the Chrome 108...
> This results in random fingerprints, which I believe defeats the purpose of the tool? If you don't mind sharing, what use case do you have which is defeated by...