file:bCGheaskGr4Q1GacwqjQYw
Truncated Wireshark Capture

I assume that if you have taken the trouble to proxy through Apache you are running in the production environment? Uncomment the line "config.force_ssl = true" in config/environments/production.rb and Tracks should generate HTTPS URLs.

Oh, actually, that option is new in Rails 3.1 I think. It will work in Tracks 2.2devel but not 2.1.x. Which version of Tracks are you running?

there is also a SSL option in site.yml. See the site.yml.tmpl for the defaults...

@Dan, I am running in production, but don't have that option. I am using Tracks 2.1.1 on Centos 6 (Rails 2.3.14).

@lrbalt, I don't see anything specific to SSL except some config options related to LDAP.

I did secure_cookies options and toggled that the true based on previous feedback. This hasn't had any effect.

Try editing line 25 of app/views/layouts/standard.html.erb. Change <%= root_url %> to <%= root_path %>. That should make the AJAX use relative paths.

@lrbalt can you please add a 2.1.1 version to Assembla?

@zoombody I've added version and a new milestone

@zoombody

I tried editing the line you requested and the change didn't have any effect. The AJAX call looked like it was timing out - visual aide just spinning.

Restarting the server after the change had no effect.

Do you have firebug installed? could you see if the ajax call is using https?
Are you using a reverse-proxy with apache or are you using passenger? The latter makes this much simpler!

In case of the first, IIRC, for ssl to be passed to a tracks server behind a proxy, you need to add

RequestHeader set X-Forwarded-Proto "https"

to apache conf.

Current Firefox makes Firebug unnecessary for that first step -- the built-in Web Console will tell you all you need to know about network requests.

any progress? Can I close this ticket?

I never ended up figuring it out and just set up a VPN for secure access. I am no longer proxying Tracks through Apache over SSL.

Please close the ticket.

ok, thanks!