Figured this one out. A program that uses WinInet was being used to set the proxy, rather than it being set manually. The program contained a slight error, such that HTTPS was effectively getting a blank proxy. This of course did not happen with manual setup, which was what I was using.
GP ----- Original Message ----- From: "Amy Anderson" <[EMAIL PROTECTED]> To: "Gary Price (ICT)" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, March 04, 2003 1:57 PM Subject: Re: [squid-users] SSL and directed HTTP proxy Also, if you are running a FW make sure that https is open for users. On Mon, 2003-03-03 at 22:15, Gary Price (ICT) wrote: > Gary Price wrote: > >> Hi > >> some of my colleagues are reporting that, if they have a HTTP > >> proxy set in their browser (IE6), they cannot access secure > >> sites (HTTPS). > > Michael Lightfoot wrote > >Have they set the "secure" option to the name and listening port of your > >proxy? > > Do you mean that if you have a HTTP proxy and you want to use HTTPS, you *must* set > the HTTPS proxy in the browser? I thought the > reported difficulty would most likely be a local networking issue rather than a > proxy issue. > > Thanks > Gary Price > ICT > > -- Amy Anderson <[EMAIL PROTECTED]>
