I am trying to publish a Remote Desktop Web Access portal through a squid reverse proxy. I use squid mainly to send the urls to the specific web server. mail.company.com goes to the mail server and rdp.company.com goes to the Remote Web site. Everything works internally, and everything works if I forward the 443 port directly to the RDP website.
When going through squid everything goes fine until I click on a RemotApp icon. When I click on the icon it tries to connect and never brings up the application. If I change the roter to forward 443 directly to my rdp web portal then I can successfully run the app. The funny thing is, while the app is running, I can go ahead and change the router back to forward packets to the rdp portal and the connection to the remote app does not break. I can even start more remote apps without a problem as long as I don't logout of the portal. Once I logout, the problem returns.
This is the rule I am using in the Squid.conf file to publish the rdp site:
cache_peer internal.name.local parent 443 0 no-query originserver login=PASS connection-auth=on ssl sslflags=DONT_VERIFY_PEER sslcafile=/etc/ssl/certs/gd_bundle-g2-g1.crt sslversion=3 name=creative
acl internal.name.local dstdomain external.name.com