[Building Sakai] Chrome 30 and HTTP

[Niebel, William (wdn5e)]

Joshua especially, I just want to get back re your "I'd be interested in the result of setting the proxyPort, scheme, and secure attributes in the AJP connector."  All evidence is that our AJP config change (diff below) completely fixes our known Chrome 30 issues without any side effects for users of the various other browsers.

Again, we have BigIP F5 handling SSL with clients and run without SSL between F5 and Apache servers.  We left that part as-is.  We got by with just the Tomcat config change in the diff and made no Apache config change.

Thanks again to all.
Bill

[root at sakai13-f conf]# diff -u server.xml.before server.xml
--- server.xml.before    2013-10-17 10:15:20.432784000 -0400
+++ server.xml    2013-10-17 10:03:36.573576000 -0400
@@ -94,7 +94,8 @@
     <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
                maxThreads="1000" minSpareThreads="50" maxSpareThreads="100"
                maxPostSize="50000000" enableLookups="true"
-               tomcatAuthentication="false" URIEncoding="UTF-8"" />
+               tomcatAuthentication="false" URIEncoding="UTF-8"
+               proxyPort="443" scheme="https" secure="true" />

     <!-- An Engine represents the entry point (within Catalina) that processes
          every request.  The Engine implementation for Tomcat stand alone

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131017/026e87b1/attachment.html