Author: markt
Date: Tue May 12 13:44:22 2015
New Revision: 1678945
URL: http://svn.apache.org/r1678945
Log:
Document why Firefox won't connect by default
Modified:
tomcat/trunk/java/org/apache/coyote/http2/Http2UpgradeHandler.java
Modified: tomcat/trunk/java/org/apache/coyote/http2/Http2UpgradeHandler.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/coyote/http2/Http2UpgradeHandler.java?rev=1678945&r1=1678944&r2=1678945&view=diff
==============================================================================
--- tomcat/trunk/java/org/apache/coyote/http2/Http2UpgradeHandler.java
(original)
+++ tomcat/trunk/java/org/apache/coyote/http2/Http2UpgradeHandler.java Tue May
12 13:44:22 2015
@@ -34,12 +34,9 @@ import org.apache.tomcat.util.res.String
* on the basis that there will never be more than one thread performing I/O at
* a time.
* <br>
- * Currently, it appears that Firefox needs to be configured with
- * network.http.spdy.enforce-tls-profile=false in order for FireFox to be able
- * to connect. I'm not sure what is going wrong here since as far as I have
- * found that only requires TLSv1.2. openssl s_client and Wireshark confirm
that
- * TLSv1.2 is used and it still doesn't work if I limit the HTTPS connector to
- * TLSv1.2. There looks to be some other restriction being applied.
+ * Note that unless Tomcat is configured with an ECC certificate, Firefox needs
+ * o be configured with network.http.spdy.enforce-tls-profile=false in order
for
+ * FireFox to be able to connect.
*
*/
public class Http2UpgradeHandler implements InternalHttpUpgradeHandler {
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
