[Building Sakai] Chrome 30 and HTTP

Niebel, William (wdn5e) wdn5e at eservices.virginia.edu
Thu Oct 17 11:29:11 PDT 2013


University of Virginia is running Sakai 2.9.1 under Tomcat 7.0.37

________________________________
From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Joshua Swink [jswink at ucmerced.edu]
Sent: Thursday, October 17, 2013 2:12 PM
To: Kevin Pittman
Cc: sakai-dev at collab.sakaiproject.org; sakai-user-request at collab.sakaiproject.org
Subject: Re: [Building Sakai] Chrome 30 and HTTP

Yes, we're using Tomcat 7 and Sakai 2.9.

Josh


On Thu, Oct 17, 2013 at 10:38 AM, Kevin Pittman <kevin.pittman at oit.gatech.edu<mailto:kevin.pittman at oit.gatech.edu>> wrote:
One question on this:  I think the folks who have spoken up about the solution below are running Tomcat 7, right?  Has anyone been successful with it under Tomcat 5.5 (and Sakai 2.8)?  I tried and couldn't get it to work, and I'd just like to get some confirmation that (as I suspect) you need a newer version of Tomcat for those settings to work.

Thanks,
Kevin
Georgia Tech Sakai Application Adminsitrator


On Thu, Oct 17, 2013 at 04:54:11PM +0000, Niebel, William (wdn5e) wrote:
> 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
>

> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

--
Kevin Pittman                              kevin.pittman at oit.gatech.edu<mailto:kevin.pittman at oit.gatech.edu>
-----------------------------------------------------------------------
Senior Systems Support Engineer        Office of Information Technology
Academic and Research Technologies      Georgia Institute of Technology
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

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


More information about the sakai-dev mailing list