[Building Sakai] Chrome 30 and HTTP

[Matt Clare]

Hi Sakai-dev,

	Have others seen issues with Chrome 30 (shipped yesterday), and HTTPS instances of Sakai and pages being blocked because the Sakai tool directed the user/Chrome to an HTTP link, not an HTTPS link?  All HTTPS proxy'ed/balence'd systems send an HTTP header to switch back to HTTPS in these instances, but Chrome 30 apparently deems this insufficient.

	At Brock University we've noted this in our production 2.8 system in the Chat Room, Media Gallery, Section Info, Statistics tools and parts of Greadbook and Resources.

	Grep'ing 2.8's source and 2.9.3's source there seems to be a number of hard-coded http://${server}/portal/tool/${tool_path}/overview.jsf type strings/URLs (less in 2.9.3) .  This would appear to be the cause of this issue (that and an over-zerlous Chrome team and the NSA). 

	My interpretation would be that there is no need for these type of URLs, either
	/portal/tool/${tool_path}/overview.jsf
	or
	//${server}/portal/tool/${tool_path}/overview.jsf
	would appear to be sufficient.

	I'm interested if others are experiencing this issue with Chrome 30, what solutions they may have, and if my interpretation is accurate.

	Thanks for your attention,

.\.\att

  ::  Matt Clare
Manager, eLearning
  Centre for Pedagogical Innovation 
Part-time Instructor
  Interactive Arts and Sciences
Brock University, Niagara Region, Ontario, Canada
http://brocku.ca/pedagogical-innovation    905 688 5550 xt 4539   Office: SBH321