A Funny Thing Happened on the Way to HTTPS

[rmike]

Greetings,

This is probably more HTTP-related than anything else, but I'd really like to understand what's going on here:

I recently instructed my DNAT'ed Zimbra box to redirect any HTTP client interface requests to HTTP/S. Doing a telnet 'mybox.mydomain.tld:80' from outside my LAN, I duly receive a 302 response telling me to try again---at my machine's internal, non routable address (192.168.2.3). However, my browser doesn't seem to mind and connects fine regardless!?

Now, where's the magic coming from?

TIA

Mike