I tested it and now I sure that WWW proxy make my Wingate crash after turn on. But Wingate only crash after WWW proxy hold a large amount of website, ex: When a client download sth from mediafile by IDM with about 16 conection or more or another website, Wingate surely will crash
It sounds like you have transparent intercepts enabled on the WWW Proxy server, so after enabling the proxy it starts catching all the port 80 NAT traffic from the clients.
As a test, can you try configuring the clients to use the proxy server manually rather than intercepting the HTTP traffic from NAT. The client computers will behave differently when they know they are talking to a WWW Proxy.
I think this is rather hard to test, because I have more than 100 client:( hic... And can you show me how to do that on my wingate? I already know that I will check "Use proxy" on client's web browser. But I think it will hard because my clients use various of web browser: firefox, safari, IE, ..
If you disable intercepts in the WWW proxy, then the clients won't go through the proxy unless configured to do so.
If you're on an AD, then you can use group policy to set connection settings for IE (which Google Chrome also uses), but for FireFox, you'd need to manually configure them.
If you're not on an AD, then yes, it would be a lot of manual configuration for a test. Personally I'm not convinced it's anything to do with connections being intercepted.
Do you have any specific policy on the WWW proxy, e.g requiring authentication etc?