I can't immediately come up with any examples where getting rid of the proxy wouldn't have some annoying side effects
-
-
so an internal service would be considered public if it's reachable over https (which should ideally be the case) and the service has a valid cert for some name in public DNS that points at it? overloading TLS cert meaning with "I trust the owners of these domains"?
-
how do you pick the trusted public-DNS resolver you need for this?
- 10 more replies
New conversation -
-
-
Work with me here: why is it wrong in the suggested configuration? TLS as backstop gets you real "publicness", no? What am I missing?
- 5 more replies
New conversation -
-
-
So long as none of your internal subdomains conflict with actual TLDs...
-
Or are you saying we can tell the difference between a resolv.conf search path and an actual TLD?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
