![]() ![]() To do this, Squid uses access control lists (ACLs). After the proxy is installed, I need to configure it.įor my live demo, I want to cache the application I am trying to demo and any other content the application needs. I'm on a Mac, so I installed the Squid HTTP proxy via Homebrew, a free package manager for MacOS. Squidman proxy install#Install and configure Squid HTTP proxyįirst, I need to install and configure the proxy. This way I can run a live demo on an unstable connection. And, I'm going to set it up to cache only the things that I want. However, I'm going to run my proxy on the same machine as my web browser. In this tutorial, I'm going to use a web proxy in a similar way: I'll cache my content and serve that cached data to my web browser. Proxies can cache data on a server closer to the user to speed up a website. Often proxying does content filtering (e.g., corporate filters, parental filters). This means you can put an intermediary between your browser and the server to do whatever you want. What if you could record your web application's use and then replay the stored responses at the right time? Luckily, it's easy to proxy HTTP, the protocol that web browsers and web servers use to communicate with each other. But what if we can't set up a local sandbox in time for our talk? What if our database is huge and complex? What if our app has animation and interactions that we can't show with screenshots? Screenshots can never fail, and local sandboxes won't fail on overloaded conference internet connections. Live demos of remote web apps are so fraught with peril that most people find other ways of presenting them. This is a bad thing to happen while you're on stage in front of 300 people. ![]() Even the most well-prepared live demo can go wrong for unforeseeable reasons. Live demos are the bane of professional speakers everywhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |