UPDATE LIST PROXY, JUNE

64.29.151.29 80
64.29.148.38 80
64.29.148.16 80
64.29.148.47 80
91.206.100.11 3128
74.208.46.168 3128
200.181.49.179 8080
115.146.20.63 80
64.29.148.49 80
212.3.135.112 3128
190.30.214.78 808
187.27.183.129 6588
78.29.34.42 808
200.97.124.214 6588
77.252.139.242 3128
64.29.148.39 80
218.169.190.153
64.29.148.25 80
189.15.7.154 6588
201.92.69.87 6588
189.46.19.140 6588
187.26.192.0 6588
203.218.86.151 808
201.68.167.16 6588
200.170.221.10 3128
200.225.171.96 6588
89.107.195.55 88
190.134.26.88 6588
201.75.23.86 3128
117.198.228.135
123.203.170.16 8088
114.137.62.15 808
201.68.42.123 6588
117.195.165.65 6588
59.93.138.3 6588
123.201.1.234 6588
125.99.20.147 6588
115.187.33.245 6588
117.197.15.50 6588
78.156.242.191 3128
87.254.152.112 6588
123.201.86.107 6588
115.240.42.196 8080
89.112.9.90 6588
123.238.143.0 6588
219.84.2.4 808
219.78.51.43 808
89.124.235.131 8080
92.45.12.2 3128
60.48.245.106 3128

Free Proxy - Fast Proxy

Free Proxy List: Fastest Proxies.
194.116.199.88:3128
91.121.12.45:3128
85.25.132.10:3128
205.188.242.3:80
24.155.96.93:80
88.255.50.114:80
222.73.17.198:80
80.94.118.20:8080
212.93.193.83:443
212.93.193.83:8082
221.9.251.19:80
64.53.84.237:80
212.118.14.195:80
81.169.188.128:3128
72.55.191.6:3128
212.118.14.197:80
212.118.128.70:8080
193.188.105.200:8080
82.194.62.200:8080
82.194.62.220:8080
193.188.105.220:8080
211.233.63.164:8080
66.198.41.11:3128
116.7.254.148:8080
80.94.118.21:8080

Types and functions of proxy

Proxy servers implement one or more of the following functions:

Caching proxy server

A proxy server can reply to service requests without contacting the specified server, by retrieving content saved from a previous request, made by the same client or even other clients. This is called caching. Caching proxies keep local copies of frequently requested resources, allowing large organizations to significantly reduce their upstream bandwidth usage and cost, while significantly increasing performance. There are well-defined rules for caching. Some poorly-implemented caching proxies have had downsides (e.g., an inability to use user authentication).

Web proxy

A proxy that focuses on WWW traffic is called a "web proxy". The most common use of a web proxy is to serve as a web cache. Most proxy programs (e.g. Squid) provide a means to deny access to certain URLs in a blacklist, thus providing content filtering. This is usually used in a corporate environment, though with the increasing use of Linux in small businesses and homes, this function is no longer confined to large corporations. Some web proxies reformat web pages for a specific purpose or audience (e.g., cell phones and PDAs).

Anonymizing proxy server

An anonymous proxy server (sometimes called a web proxy) generally attempts to anonymize web surfing. These can easily be overridden by site administrators, and thus rendered useless in some cases.

Transparent and non-transparent proxy server

The term "transparent proxy" is most often used incorrectly to mean "intercepting proxy" (because the client does not need to configure a proxy and cannot directly detect that its requests are being proxied). Transparent proxies can be implemented using Cisco's WCCP (Web Cache Control Protocol). This proprietary protocol resides on the router and is configured from the cache, allowing the cache to determine what ports and traffic is sent to it via transparent redirection from the router. This redirection can occur in one of two ways: GRE Tunneling (OSI Layer 3) or MAC rewrites (OSI Layer 2).

Forced proxy

The term "forced proxy" is ambiguous. It means both "intercepting proxy" (because it filters all traffic on the only available gateway to the Internet) and its exact opposite, "non-intercepting proxy" (because the user is forced to configure a proxy in order to access the Internet).

Forced proxy operation is sometimes necessary due to issues with the interception of TCP connections and HTTP. For instance interception of HTTP requests can affect the usability of a proxy cache, and can greatly affect certain authentication mechanisms. This is primarily because the client thinks it is talking to a server, and so request headers required by a proxy are unable to be distinguished from headers that may be required by an upstream server (esp authorization headers). Also the HTTP specification prohibits caching of responses where the request contained an authorization header.