This window allows you to configure two types of proxy servers, though which Firestorm can connect to SL.
The HTTP proxy is specifically for routing HTTP traffic meant to be viewed inworld via the Media Browser or Shared Media (and potentially "other" HTTP traffic). It is not necessary to set up this proxy in order to connect to Second Life from inside a closed network, but you will not have access to web content. If you need to set up an HTTP proxy for your normal web browser, you probably need to set up an HTTP proxy for Second Life as well.
To configure an HTTP proxy for web pages in the Proxy Settings window:
The SOCKS proxy is responsible for routing UDP traffic (and potentially "other" HTTP traffic) between Second Life and resources outside your closed network. If you are on a closed network, such as at a school or corporate office, you must configure a SOCKS proxy in order to connect to Second Life.
To configure a SOCKS 5 proxy for UDP traffic in the Proxy Settings window:
In addition to web and UDP traffic, Second Life uses HTTP for a few other purposes, such as loading your inventory and loading textures on objects. You may choose to route this “other” HTTP traffic through either an HTTP proxy or SOCKS 5 proxy. If you have configured both types of proxies, try experimenting with each to figure out which one provides the best inventory and texture loading speeds.
To select a proxy for other HTTP traffic, choose from one of the available radio buttons under Other HTTP traffic proxy in the Proxy Settings window. You cannot select a proxy you have not yet configured.
Proxy servers do not currently aid the following features in getting through your network's firewall:
See this page for documentation on Firestorm 4.6.9 (42969) and earlier.