On 21.09.2010 21:32, Nikos Mavrogiannopoulos wrote: : > Why wouldn't it be? Did you notice any issues? mod_gnutls only offers > the secure layer. The HTTP is still handled by apache thus anything that > worked without mod_gnutls should work with it. :
Another hint that mod_gnutls is the culprit: the headers of the responses in both cases (mod_ssl, mod_gnutls) are the same. The difference is, that apache with mod_gnutls closes the connection after the response while apache with mod_ssl does not. mod_gnutls: H: HTTP/1.1 200 OK H: Date: Wed, 22 Sep 2010 03:34:51 GMT H: Server: Apache/2.2.16 (Debian) H: Vary: Accept-Encoding H: Keep-Alive: timeout=60, max=100 H: Connection: Keep-Alive H: Transfer-Encoding: chunked H: Content-Type: text/plain mod_ssl: H: HTTP/1.1 200 OK H: Date: Tue, 21 Sep 2010 11:15:38 GMT H: Server: Apache H: Keep-Alive: timeout=15, max=99 H: Connection: Keep-Alive H: Transfer-Encoding: chunked H: Content-Type: text/plain SSL_VERSION_LIBRARY=GnuTLS/2.10.1 SSL_VERSION_INTERFACE=mod_gnutls/0.5.8 (the same for official debian packages from testing, gnutls 2.8.6, mod_gnutls 0.5.6) Hardy _______________________________________________ Modules mailing list Modules@lists.outoforder.cc http://lists.outoforder.cc/mailman/listinfo/modules