Luke Francl wrote: > I can't say for sure if refresh_to will solve your problem > because we've never encountered it before (until I saw > your message I would not have thought a 302 between > two secure pages would cause this problem).
Where I'm seeing the problem actually not between two pages, but between two methods. The process is a) page submits to controller 1, action 1 b) controller 1, action 1 does its thing, then redirects to controller 2, action 1 c) controller 2, action 1 renders new page I'm pretty sure the problem is that the redirect_to in (b) is sending a 302 header. This is really way over my pay grade. So I'll ask. Does a 302 header include info on _where_ it's being moved to? Like maybe there's an http: prefix in there this I could override somehow? Do maybe routes figure in with this somehow? I definitely plan to give the plugin a try. Thanks much for letting me know about it. To be honest though, if there's an easier way like adding a line or two to routes.rb that would solve this problem, I'd definitely take that over changing a bunch of redirect_to lines of code. Thanks again, Luke. I apprecitate you help very much. Best regards, Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
