My answer is more about Citrix than Squid it-self.
The new Citrix Client (6.3) accept HTTPS encapsulation though CONNECT
method (secure proxy bypassing).
It works perfectly and indepandantelly of Metaframe version (I tested
1.8 and XP with that).
You should add key to Nfuse template or directly to your ICA file
A correct result is :
[WFClient]
Version=2
SSLCiphers=All
SSLCommonName=10.0.0.1:8080
SSLEnable=on
SSLProxyHost=10.0.0.1:8080
[ApplicationServers]
the application=
[the application]
Address=192.56.20.10:443
AutologonAllowed=ON
BrowserProtocol=HTTPonTCP
ConnectType=2
DoNotUseDefaultCSL=On
ICAPortNumber=443
InitialProgram=#"Test"
ProxyHost=10.0.0.1:8080
ProxyType=Secure
SecureChannelProtocol=Detect
SavePNPPassword=Off
TransportDriver=TCP/IP
UseAlternateAddress=1
WinStationDriver=ICA 3.0
#+ for Microsoft proxies :
ProxyAutoConfigURL=http://proxy/pacfiles/config.pac
ProxyBypassList=http://proxy/pacfiles/config.pac
-----Original Message-----
From: Colin Foss [mailto:Colin.Foss@efi.com]
Sent: 29 octobre, 2002 02:53
To: squid-users@squid-cache.org
Subject: [squid-users] Squid and Citrix Published Application
Has anyone been able to connect to a Citrix published application
through any version of Squid? I have a situation where a client is
using Squid 2.4 Stable 4 and cannot use the application.
I have duplicated the client OS setup and firewall setup but am unable
to reproduce the error they get.
Any help? https://portal.efi.com/defect/ssl-pollux-clock.htm is the
published application we use for testing.
TIA.
Colin Foss
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:56 MST