Sonia Appasamy c6a274611e client/web: use Tailscale IP known by peer node ... Throughout the web UI, we present the tailscale addresses for the self node. In the case of the node being shared out with a user from another tailnet, the peer viewer may actually know the node by a different IP than the node knows itself as (Tailscale IPs can be configured as desired on a tailnet level). This change includes two fixes: 1. Present the self node's addresses in the frontend as the addresses the viewing node knows it as (i.e. the addresses the viewing node uses to access the web client). 2. We currently redirect the viewer to the Tailscale IPv4 address if viewing it by MagicDNS name, or any other name that maps to the Tailscale node. When doing this redirect, which is primarily added for DNS rebinding protection, we now check the address the peer knows this node as, and redirect to specifically that IP. Fixes tailscale/corp#16402 Signed-off-by: Sonia Appasamy <sonia@tailscale.com>		2023-12-14 16:36:33 -05:00
..
tailscale	client/web: indicate if ACLs prevent access	2023-12-01 16:51:12 -08:00
web	client/web: use Tailscale IP known by peer node	2023-12-14 16:36:33 -05:00