Frederick Cheung wrote: > On Jun 10, 1:45�pm, Perry Smith <[email protected]> > wrote: >> Frederick Cheung wrote: >> >> > apache/nginx rewrite rules can do this >> >> I'm worried about redirects. �The server is behind a firewall. �The >> browser thinks that foo.outside.com is different from foo. �If I am >> authenticated to foo.outside.com and then foo happens to ask for >> authentication, the browser will ask me again instead of just sending >> what it already has. >> > in that case it may be simpler to just fiddle the HTTP_HOST variable
Thats what I'm doing. Its actually a sequence of variables. I looked at how "host" was derived when a url rewrite is done. Its the forwarding host if set (which hit is in my case due to my apache set up), else HTTP_HOST if set, else HTTP_SERVER if set, else .... Its working at this point. The alternative would be to pass :host => xxx in the hash when the cache fragments is created and deleted. That seems the safest but it hits multiple places. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
