You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/client/web
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>
12 months ago
..
build
src client/web: fix redirect logic when accessing login client over TS IP 12 months ago
assets.go client/web: only add cache header for assets 12 months ago
auth.go client/web: use prefs.ControlURLOrDefault from controlSupportsCheckMode 12 months ago
index.html client/web: use CSP hash for inline javascript 12 months ago
package.json
qnap.go
styles.json
synology.go
tailwind.config.js
tsconfig.json
vite.config.ts
web.go client/web: use Tailscale IP known by peer node 12 months ago
web_test.go client/web: keep redirects on-site (#10525) 12 months ago
yarn.lock