Lan?

Yes which leads to the kind of hilarious issue I saw this morning where Chrome reported a CORS issue doing an HTTP load from a machine to itself, claiming that it needed HTTPS to load from a less-public context than the page.

The reason? The initial page load happened over IPv6 which has a real public address, and was therefore public context, while the resource it tried to load was loading (for whatever reason) over IPv4 which was an RFC1918 address behind NAT and was hence considered a private context.