You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Running mubeng like this:
./mubeng --address 0.0.0.0:9899 --file proxies.txt --check --rotate 2 --method random --daemon
My proxies.txt looks like this:
http://127.0.0.1:9900 http://127.0.0.1:9901 http://127.0.0.1:9902 http://127.0.0.1:9903 http://127.0.0.1:9904
If I use one of my proxies directly, using
curl --proxy localhost:9902 https://httpbin.org/ip
it looks like this:
origin": "██.██.██.██" }
But when I run this through mubeng, using
curl --proxy localhost:9899 https://httpbin.org/ip --insecure
(I have to add
--insecure
, because otherwise I get an SSL error. Which I don't need to do when using my proxy directly.)I get this instead:
origin": "127.0.0.1, ██.██.██.██" }
I think mubeng is adding a "X-Forwarded-For" header (which does show up if I use
--verbose
).I have two questions:
How can I remove the 127.0.0.1 and/or the X-Forwarded-For header from showing up?
What can I do to make requests through mubeng without getting SSL errors?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions