[squid-users] Remote Desktop Gateway thru Squid.

Amos Jeffries squid3 at treenet.co.nz
Thu Oct 22 09:06:47 UTC 2015

On 22/10/2015 7:43 a.m., Sebastien.Boulianne wrote:
> Hi all,
> Im looking to use my Remote Desktop Gateway with my Squid.
> I tried this config but it didnt work.
> ### SITE
> cache_peer site.domain.qc.ca parent 443 0 no-query originserver ssl sslflags=DONT_VERIFY_PEER name=site
> acl sitehttps url_regex ^https://site\.domain\.qc\.ca
> http_access allow www443 sitehttps
> http_access allow rdp sitehttps
> cache_peer_access site allow www443 sitehttps
> cache_peer_access site allow rdp sitehttps
> acl sitehttp url_regex ^http://site\.domain\.qc\.ca
> http_access deny sitehttp
> deny_info 302:https://%H%R sitehttp
> Im curious to know if someone ever did that.
> Thanks you very much in advance.
> 1445443415.045      3 ............ TCP_MISS/404 1580 RDG_OUT_DATA https://site.domain.qc.ca/remoteDesktopGateway/ - FIRSTUP_PARENT/............ text/html
> 1445443415.116      2 ............ TCP_MISS/401 450 RPC_IN_DATA https://site.domain.qc.ca/rpc/rpcproxy.dll? - FIRSTUP_PARENT/............ text/plain
> 1445443415.182      3 ............ TCP_MISS/401 450 RPC_OUT_DATA https://site.domain.qc.ca/rpc/rpcproxy.dll? - FIRSTUP_PARENT/............ text/plain
> S├ębastien

Like Yuri said Squid is not designed to be compatible with every
protocol. Just HTTP and where possible HTTP based ones. So RDG and RPC
are only supported so far as they obey HTTP protocol requirements (ie
RESTful principles and behaviour).

That said, the above log lines look to me like they are working fine. At
least as far as Squid is concerned.
* The 404 is a server API being tested and found disabled or unavailable.
* The 401 is the server requiring authentication from the client before
RPC access is permitted. Which is fine and good. I would be worried if
it did not.
* all requests are being sent via the cache_peer.


More information about the squid-users mailing list