-
Looking for HSC notes and resources? Check out our Notes & Resources page
Real IP address of the client (1 Viewer)
- Thread starter axeaxe
- Start date
lol i think ur in the wrong forum... try http://forums.jinx.com/ 
or google ur question, but im sure yes u can, but ud have to be rarther serz about wanting to know it
or google ur question, but im sure yes u can, but ud have to be rarther serz about wanting to know itTechnically, no. The point of an application proxy (such as a HTTP proxy or a DNS forwarder) is to relay the traffic between the client and the server. The server sees the traffic as coming from the proxy's IP address, not from the client's IP address.
In practice, some proxies insert additional data into the proxied traffic to identify the client. A HTTP proxy may add a X-Forwarded-For line to the HTTP header containing the client's IP address. The presence of this can't be relied upon: some HTTP proxies don't add it, it could be false, if the user is on a NATed network the address will not be unique, and a caching HTTP proxy may hand out the page to more than just the initial requesting client.
Some protocols simply don't have enough expandability to allow the client's IP address to be inserted. For example, a DNS forwarder.
A transparent HTTP proxy is a proxy which works by the router intercepting the HTTP traffic and passing that traffic to the proxy server. This has the strong advantage that the client need not their web browser configuration (thus the name "transparent" -- from a user configuration point of view it is not as if the proxy is there).
Intercepting the HTTP traffic at the router also allows the requestor's IP address to be used (assuming that this is not a NATed address). This is desirable because the web site sees the real address of the initial client, but undesirable because a caching proxy server may later give content customised for that address to other clients. Because of this trade-off configurations vary between ISPs.
In practice, some proxies insert additional data into the proxied traffic to identify the client. A HTTP proxy may add a X-Forwarded-For line to the HTTP header containing the client's IP address. The presence of this can't be relied upon: some HTTP proxies don't add it, it could be false, if the user is on a NATed network the address will not be unique, and a caching HTTP proxy may hand out the page to more than just the initial requesting client.
Some protocols simply don't have enough expandability to allow the client's IP address to be inserted. For example, a DNS forwarder.
A transparent HTTP proxy is a proxy which works by the router intercepting the HTTP traffic and passing that traffic to the proxy server. This has the strong advantage that the client need not their web browser configuration (thus the name "transparent" -- from a user configuration point of view it is not as if the proxy is there).
Intercepting the HTTP traffic at the router also allows the requestor's IP address to be used (assuming that this is not a NATed address). This is desirable because the web site sees the real address of the initial client, but undesirable because a caching proxy server may later give content customised for that address to other clients. Because of this trade-off configurations vary between ISPs.
Last edited: