A famous ISP use NAT + proxy fot http protocol. Obviously https can’t be cached, so a proxy isn’t so usefull as in http. Nothing extrange by the moment.
This ISP didn’t use NAT for https, and here comes the problem, if you’re connected with that ISP you may present a different IP to a webserver if you use single http or https, ’cause you IP it’s being translated by NAT on http and don’t on https. Yes! two differents IP for a single machine…
If you’re a ISP customer may you don’t feel this as an error, but if you’re webmaster -as I ‘m- you go crazy following sessions with two diffrents IP’s. .. damn ISP. It’s so difficult use NAT for everything ? or didn’t at all?
I’m using NAT at home, for my internal LAN -over all protocols used- and goes fine. Yes, I know it’s no the same, but again:
- It’s so difficult use NAT for everything ? or didn’t at all?