Ok, I've worked out what's happening. When you're on the page that has been forced to be ssl, then all of your links that use /something will now pick up the https.
So all my main navigation links are pointing to https I can't change them as the site won't work in development then or on any testing and staging servers. um, this is a right pain in the arse. Anyone know a way around it? On Friday, 12 July 2013 11:00:24 UTC+1, vanderkerkoff wrote: > > Hello everyone > > rails3.2 ruby 1.9.3 nginx 1.5 passenger 4 > > I'm using > force_ssl<http://apidock.com/rails/v3.2.13/ActionController/ForceSSL/ClassMethods/force_ssl>in > a controller on our site, and certain actions within that controller. > > force_ssl :only => [:show, :list, :toilet] > > This works great, I can go to the site via http, no problems, and when I > click on the link responding to the controller the https kicks in, and is > also active on the other actions specified within that controller. > > The issue I'm getting is after using that controller, which forces https, > clicking on any other links within that site still uses https. > > That's not what I imagined to happen, and may cause an issue. > > Is the browser caching the https traffic and assuming to use it again? > > Is there any way around this? > > Any help, greatly appreciated. > > V > > > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/59dff581-04cc-46cd-a68e-a19e57639b66%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
