ipvfoo
ipvfoo copied to clipboard
pmarks-net
Proxy Server Getting Detected Instead
What steps will reproduce the problem?
1. Install a local proxy
2. Setup your browser to use your proxy
3. Refresh/Visit a website
What is the expected output? What do you see instead?
The extension should be showing the IP addresses of the site. But instead, it
is showing the local proxy's IP address.
What version of the product are you using? On what operating system?
0.8.0
Please provide any additional information below.
none
Original issue reported on code.google.com by [email protected] on 10 Oct 2011 at 6:20
What other behavior would you suggest? Are you aware of a proxy server that
can report the HTTP server's IP address back to its clients?
Original comment by [email protected] on 10 Oct 2011 at 7:42
A proxy server could theoretically inject headers into its HTTP responses
containing the server's IP address (with additional magic to handle caching.)
But I'm not aware of any proxy servers that do this, nor of any standardized
headers.
Chrome doesn't have an API for performing raw DNS lookups, and even if it did,
that would mean extra network traffic and code complexity. It would be
possible to run a separate HTTP<->DNS proxy daemon, but that's a bit silly.
So I'm going to mark this bug as not currently feasible.
Out of curiosity, which proxy server software are you running?
Original comment by [email protected] on 14 Oct 2011 at 8:56
- Changed state: WontFix
Sorry for the late reply.
Was thinking maybe a fallback to something like how the Firefox Add-On "ShowIP"
is doing it?
I'm using privoxy, not exactly for proxy purposes as it was intended, more on
to redirect access to TOR, I2P, and FreeNet.
Original comment by [email protected] on 15 Oct 2011 at 3:36
Pointing to ShowIP is a non-starter. If a ShowIP-style extension were possible
using the Chrome APIs, then I probably never would've written IPvFoo.
Original comment by [email protected] on 15 Oct 2011 at 4:11
Issue 12 has been merged into this issue.
Original comment by [email protected] on 2 Oct 2012 at 4:52
Issue 14 has been merged into this issue.
Original comment by [email protected] on 16 Jan 2013 at 8:06
Issue 14 (SOCKS) is not exactly the same as issue with HTTP proxy. In SOCKS
works at lower level than HTTP proxy.
Original comment by [email protected] on 16 Jan 2013 at 8:26
It's still the case that IPvFoo only sees the address provided by Chrome.
I haven't studied Chrome's SOCKS code, but if it's using the "Domain Name"
address type, then even the browser doesn't know the server's true address.
Original comment by [email protected] on 16 Jan 2013 at 8:39