-
-
Notifications
You must be signed in to change notification settings - Fork 610
Auto-detect IPv4 / IPv6 listen based upon --hostname arg #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
running proxy.py on one machine
configure firefox on second machine
please advise |
@mbatrawi As commented on separate thread, I don't think your requests even reach PR #76 fixes the original concern raised in this issue. You should be able to simply use |
I am using proxy master
Python 3.6 proxy.py —port 12500 —hostname 0.0.0.0
On 22 Sep 2019, at 5:57 AM, Abhinav Singh <[email protected]> wrote:
@mbatrawi<https://github.com/mbatrawi> As commented on separate thread, I don't think your requests even reach proxy.py on the other machine, kindly verify your setup.
PR #76<#76> fixes the original concern raised in this issue. You should be able to simply use --hostname 0.0.0.0 without need of also passing --ipv4 flag.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#71?email_source=notifications&email_token=ANGHGNFMMKBN6GKEF6KJM2TQK3GHJA5CNFSM4IYF2D3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7I42PY#issuecomment-533843263>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANGHGNC6O7I5F7H6R5YFKHDQK3GHJANCNFSM4IYF2D3A>.
|
kata@triton ~ $ clear
kata@triton ~ $ curl -v -c 127.0.0.1:12509 http://httpbin.org/get
* Trying 3.222.220.121...
* TCP_NODELAY set
* Connected to httpbin.org (3.222.220.121) port 80 (#0)
GET /get HTTP/1.1
Host: httpbin.org
User-Agent: curl/7.57.0
Accept: */*
< HTTP/1.1 200 OK
< Access-Control-Allow-Credentials: true
< Access-Control-Allow-Origin: *
< Content-Type: application/json
< Date: Sun, 22 Sep 2019 05:03:22 GMT
< Referrer-Policy: no-referrer-when-downgrade
< Server: nginx
< X-Content-Type-Options: nosniff
< X-Frame-Options: DENY
< X-XSS-Protection: 1; mode=block
< Content-Length: 200
< Connection: keep-alive
<
{
"args": {},
"headers": {
"Accept": "*/*",
"Host": "httpbin.org",
"User-Agent": "curl/7.57.0"
},
"origin": "194.14.45.10, 194.14.45.10",
"url": "https://httpbin.org/get"
}
* Connection #0 to host httpbin.org left intact
kata@triton ~ $
On 22 Sep 2019, at 5:57 AM, Abhinav Singh <[email protected]> wrote:
@mbatrawi<https://github.com/mbatrawi> As commented on separate thread, I don't think your requests even reach proxy.py on the other machine, kindly verify your setup.
PR #76<#76> fixes the original concern raised in this issue. You should be able to simply use --hostname 0.0.0.0 without need of also passing --ipv4 flag.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#71?email_source=notifications&email_token=ANGHGNFMMKBN6GKEF6KJM2TQK3GHJA5CNFSM4IYF2D3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7I42PY#issuecomment-533843263>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANGHGNC6O7I5F7H6R5YFKHDQK3GHJANCNFSM4IYF2D3A>.
|
@mbatrawi Great, looks like it worked out for you :) Thanks |
But I configured firefox as usual
I can’t browse
Regards
On 22 Sep 2019, at 10:34 AM, Abhinav Singh <[email protected]> wrote:
@mbatrawi<https://github.com/mbatrawi> Great, looks like it worked out for you :) Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#71?email_source=notifications&email_token=ANGHGNFS7DOKO3UUN44HPUDQK4GY5A5CNFSM4IYF2D3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7I7QGI#issuecomment-533854233>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ANGHGNEEWLTKRIFG5GI73HDQK4GY5ANCNFSM4IYF2D3A>.
|
@mbatrawi That sounds more like a browser configuration issue to me. At-least now you are able to hit |
For brief background see #68 (comment)
The text was updated successfully, but these errors were encountered: