On Thu, 18 Mar 2004, Eric Geater 3/17/03 wrote: > I have a lone computer that must communicate via secure sockets to a web > server. Communication starts with our machine on port 80, and the > server responds on port 80. Then it goes to SSL and attempts to > negotiate communication on port 6847. Eventually, though, the server > times out because my end (apparently) doesn't allow the connection.
What does access.log say? Is the browser configured to use the proxy for SSL? Regards Henrik
