Notice that if I put for my client a proxy which is my MT proxy IP , it forwards everything to web-proxy or I get https from the web proxy but if I user is on port 80 he can gets only HTTP port 80 but HTTPS got directly .. they told me that i want to forward my https to web proxy so how can we forward s https to web-proxy .
If you redirect port 443 it will not actually proxy the request - the proxy will merely pass on the request and not cache it. There is probably no benefit in caching HTTPS. Also how would your users feel knowing that there might be a chance of their secure transactions being cached (even if you know it is not so)?
I already used this rule before I post this topic , i got msn and everything uses SSL down …
Notice that if I made some settings at our clients or If i put proxy for explorer and passes through local .. surfing gets much better with it but if I left it at normal settings which is default port 80 it will only cache HTTP requests , another thing is do not forget that some pictures and exe files are being downloaded from HTTPS .
What do you think the best solution for HTTPS request and how can we forward it to cache ?
do not try to forward https to proxy, you would have problems with signing in to email or bank account. But for FTP, you could try, but you need to increase the maximum cache size of your proxy
So do you mean that all versions do not support Transparent FTP .
Is there any idea to cache https , actually not all https but only pictures or extensions like exe as it seems that most websites are securing their files by HTTPS .
For pure security reasons you can’t cache HTTPS and for a good reason.
Most secure sites will not accept the connection in the first place and those that do are NOT secure anyway. Please read documention on why it is not suppose to work from squid-cache for example.
It is pretty simple and is due to the man-in-the-middle attacks, making a supposed secure connection insecure. Any proper web proxy server has not implemented this and never will.
But if I changed my settings to Transparent Mode = no and apply new settings for clients by putting the same proxy for all protocols : Http , Secure , FTP , Socks …
after changing , i found some changes with HTTPS , much faster than before … so i knew that is from cache since you can manage access or filter caching ..
We use MT WEB-PROXY only for filtering web content. The problem is that most of the web servers (including my company’s) will accept https connections by default wich then bypasses my proxy and the user can visit the forbidden site anyway…
Anyway , i have finished our servers .. if anyone requested the blocked websites via 80 or 443 then he/she will get a website that shows access denied .
all it was done by blocking websites that are on access-list .