> > Though you probably want to test the https-to-http redirect case (and not > follow)... was that it?
Yes, that was my motivation for using https. Although, ignoring SSL error did not fix the issue completely. Now I started seeing a RemoteHostClosedError on the client side. Debugging it I found that the bytes written by the server (on the SSL socket), never really reached the client. And since we do an immediate disconnect after writing, the client was getting the above error. The problem can be fixed, if we do a flush() on the server socket. I'm not sure what the side-effects may be, if any. Thoughts? -mandeep > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
