If the document roots for the domais are set right, you don't need to
anything in symfony, domain for link_to() and like functions are
detected at runtime. You just need to set up DNS and apache's vhosts.
Another thing is that you propably want to set some settings different
for each domain, you can use filter for this.
-- Marek
On 25. Okt, 12:35 h., Andreas Stephan <[EMAIL PROTECTED]>
wrote:
> Marek,
> that looks like an interesting an especially simple approach. I will
> have a look into that.
> Does anyone know, if /how I could implement a solution based on
> rewrite rules, eg. have a urlwww.foreign-domain.comin the browser
> address bar but really use a subdomain
> like foreign-domain.rootsite.com? If possible, could I use the symfony
> routing system for this or would I have to "hard-code" it into my
> htaccess file using mod-rewrite?
>
> Andy
>
> On Oct 25, 9:07 am, Marek <[EMAIL PROTECTED]> wrote:
>
> > Using javascript:
>
> > on the custom domains:
> > if(is_login_cookie_set() == false) {
> > ?>
> > <script src="http://maindomain.com/checklogin.js";></script>
> > <?php }
>
> > and checklogin.js sets the login cookie using javascript.
>
> > If javascript is off, redirect to login page with return=url
> > parameter, based on this parameter display an image from the custom
> > domain with session id in the url. This image will be in fact a php
> > script that sets the session cookie. The user might not even need to
> > login second time, as the login page might find out he's logged in and
> > display the image right away.
>
> > -- Marek
>
> > On 24. Okt, 10:29 h., Andreas Stephan <[EMAIL PROTECTED]>
> > wrote:
>
> > > Hi, we are building a service, where users can create their own social
> > > networks. We have implemented a single sign on mechanism for all
> > > subdomains. In the future we want to let community creators to use
> > > their own domain names. Does anyone have an idea how to make the
> > > single sign on mechanism work cross domain?
> > > It looks like passing the session ID as a GET-parameter between
> > > different servers and cloning the necessary cookies respectively seems
> > > to be an option, but that looks fairly complicated to implement in
> > > symfony's routing system. Moreover, we have to prevent adding this
> > > parameter to all normal urls in order to be google friendly and keep
> > > user friendly urls at least in the area, where you do not have to be
> > > logged in. Any suggestions how to achieve such behaviour with symfony?
> > > Or is there an easier way to achieve the same behaviour using rewrite
> > > rules?
>
> > > Cheers, Andy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" 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/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
