Has anyone else had anamolous issues with ASP.NET 1.0 over IE/HTTPS
with SQUID 2.5 STABLE6?

I have a funny feeling it has to do with the configuration, or
lack-there-of, on the SQUID server.

Would a mis-compile without the --enable-ssl, or not using a client
certificate for the SQUID server cause intermittent errors with ASP 1.1
or HTTP/1.1|SSL?

I ready somewhere that ASP 1.1 with IIS 5.5+ relies on HTTP/1.1 and/or
TLS/1.0 for chunked packets, and that this might confuse a
mis-configured SQUID web proxy (or an HTTP/1.1|TLS/1.0 incapable proxy
server).

Nonetheless, I do not have control of the system, or access to it, but
I've been tasked with coming up with a solution.  I do have a copy of
SQUID 2.5 STABLE6 on my box, and I have the same issues with a "Page
cannot be displayed" error in IE 5.5 for a .NET 1.0 app only on certain
pages over the open internet, and only so often... but it works just
fine on ISA 2004, which handles chunked data.

Could the functionality stated in RFC2817 "HTTP/1.1 Update for TLS/1.0"
apply to the error in SQUID / IE5.5+?
Anybody have any ideas?

Thanks,
ape

[ Post a follow-up to this message ]