This forces squid to always fetch an entire object, even if you only want a piece of it. This allows the viewer to fetch portions of the texture rather than the whole thing.įor the purposes of caching, we actually want the whole texture: Now, because of discard levels in the textures, most of the fetching that the viewer does is by Range-requests. If you just want to get HTTP textures across your corporate firewall efficiently, you can stop there as far as the squid configuration part goes, and just skip down to ‘Capturing the requests’. Next, we want to make sure that squid allows requests to be made to port 12046 which is the port Second Life’s HTTP textures are running on:’Īcl Safe_ports port 12046 # Second Life HTTP textures So, add the following line to the configuration: For the purposes of this guide, we’ll use 3178. We’ll add a new port for handling transparent proxying. Now in nf you’ll find that the port defaults to 3128. It might already be, which is even better.
#Sl cache viewer how do i find cache how to
A knowledge of how to set up and configure squid.įirst, get squid3 installed on your gateway system.
#Sl cache viewer how do i find cache windows
Really, if you’re running Windows, you should already have one running as a firewall for you, because Windows just isn’t safe to directly connect to the Internet on its own.
It’s particularly handy if you’re behind a corporate or educational firewall and your network admin would prefer to proxy rather than open up a new port. There are benefits to this and some downsides. I’ve been doing some experiments with HTTP textures, and yes, you can proxy/cache them external to your machine even though the viewer doesn’t support it.
0 kommentar(er)
