> > It *migh* be the way IE uses ssl, it is broken, I think.
>
> IE? broken? NEVER. </sarcasm>
Always! </serious> :)
> Try with mozilla or opera or some such, and see if the issue shows up
> there. If not, then you've pinpointed the problem without any
> additional effort.
>
> http://www.mozilla.org <-- free, open source, great :)
> http://www.opera.com <-- free download (with ads) or register.
I have already verified it doesn't happen with any known browser
other than the latest IE6 (for sure, possibly older versions as well, but
that is un-verified), and then only when running on Windows XP. So it is
definitely an IE problem, it's just a problem I'm hoping to find a
workaround for, since IE + XP = the most common browser platform on the
planet (used by 100% of my clients - not all of which are happy with a
solution like 'install mozilla and quit bugging me' :)
Further update - results very much do seem to point to something
in how IE does some function or another when using an SSL connection.
When using the CGI installed on a un-encrypted webserver, I have yet to
find a client who is able to duplicate the problem. :( Not out of
potentials yet, but enough people have not been able to duplicate that I'm
pretty convinced nobody else is going to be able to either.
Thanks for the braincycles everyone who's given/is giving my
problem some thought. I'll continue to report back as I have more
info/more debugging data.
--
Jack
-------------------------------------------------------------------------------
When man calls an animal "vicious", he usually means that it will attempt to
defend itself when he tries to kill it.
-------------------------------------------------------------------------------
