Not correctly inferring protocol with SSL, unless force_ssl is set

[chrisvfritz]

Just tried the latest turbolinks on a site with SSL and every link on the page produced mixed content errors, resulting in all internal page visits being blocked by the browser. Yikes!

It may also be worth noting that I'm using Turbolinks.enableTransitionCache().

[chrisvfritz]

It looks like that app wasn't forcing SSL in production.rb via config.force_ssl = true. It is now and turbolinks works! I'd hope not too many apps are using SSL without that option, but I think I'll rename the issue instead of closing it, because I'd expect at least one of these to happen:

• When turbolinks is installed, but SSL is not forced either in the config or controller, pages served via SSL 500 with a useful error logged. This might not be feasible, because I can imagine cases where turbolinks might just not be used on SSL pages and this could be difficult to detect.
• Turbolinks uses the same protocol as the current page for relative links, just like normal links do. (This would be my personal preference.)

[Deuteu]

difficult to detect

In my case on http page, turbolink changes it to https in the url so easy to detect but unwanted so second point would be great.