[General] FT Cache Compromised (Again)

[Bashar Al-Abdulhadi]

Majed B. wrote, On 12/04/2008 11:10 AM:

> The client that is using a proxy will go through port 3128 for
> example, but I think the proxy itself will go through the web over
> port 80 again, which is why it gets filtered.
>   
exactly this is what i meant, the proxy will access web and will be 
filtered, thats why proxy should be outside to access web easily

we have a friend on the list who uses VPN and its way faster as i 
noticed than proxy, care to elaborate yal 7abeeb ? ;)


> My point was: since you have 2 machines, one local & one remote, just
> configure the local proxy to route all traffic (route not cache and
> forward requests) to the remote one. This way you're no longer going
> through your ISP.
>
> It's hooking the remote machine with the local through VPN, and the
> remote box is the gateway to your proxy.
>
> On Thu, Dec 4, 2008 at 10:59 AM, Bashar Al-Abdulhadi
> <bashar at kuwaitnet.net> wrote:
>   
>> having local machine when accessing the internet via your ISP via port 80 it
>> will be triggered by your ISP's caching system and wwill be filtered again,
>> so no real use of it, thats why when you put a remote box to connect to it
>> via non-default http port then that remote box goes to the internet
>>
>>
>> for example from your local machine do wget www.skype.com it will show FT's
>> blocked page it will be the same when squid/proxy access the internet from
>> the machine
>>     
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3262 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://oskw.org/pipermail/general_oskw.org/attachments/20081204/eed58e6b/attachment.bin>