Well, the idea is that the enterprise would have full control over blocking via policy, in addition to any default restrictions.
for what sorts of public resources exactly? I assume you're not just talking about CDNs? is the intent to do things like "generate link previews in a messenger client-side"?
-
-
No, by "public" I'm literally referring to anything that I could hit with an anonymous HTTP GET from a random host sitting outside of your network. That's the kind of stuff that people proxy all over the place today.
-
can you be more specific than "all over the place"? which proxying usecases do you want to replace? AFAIU some sites specifically use a proxy for privacy reasons, and for others (like messaging sites), letting the sending client generate the preview causes authenticity problems
- 8 more replies
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.