www.x.com and x.com -problem.

Next topic

Author	Message
Jerry Jalava	Wednesday 31 March 2004 1:22:21 am Hi, We use an 3rd party menu in our portal and we've got in to this problem: - User comes to our site at x.com and logs in. - After he/she clicks some link in the menu it sends him/her to www.x.com/content - The session disappears (login is requested again) The same thing goes otherway around also. Our menu (javascript) has all links pointing to www.x.com. eZ renders all urls depending on the uri that you come in (x.com/www.x.com), so we can't change the menu to be as x.com 'cause then the other links wouldn't work either... Is this a bug or something else? Regards, Jerry
Bård Farstad	Wednesday 31 March 2004 1:36:59 am The reason for this is that cookies does not work on different domains. So if you want to use both domain.com and www.domain.com you should use relative url's in your links, this should solve the problem. Then the user will always to linked to the current domain. --bård Documentation: http://ez.no/doc

Author

Message

Wednesday 31 March 2004 1:22:21 am

Hi,

We use an 3rd party menu in our portal and we've got in to this problem:
- User comes to our site at x.com and logs in.
- After he/she clicks some link in the menu it sends him/her to www.x.com/content
- The session disappears (login is requested again)

The same thing goes otherway around also.

Our menu (javascript) has all links pointing to www.x.com.

eZ renders all urls depending on the uri that you come in (x.com/www.x.com),
so we can't change the menu to be as x.com 'cause then the other links wouldn't work either...

Is this a bug or something else?

Regards,
Jerry

Bård Farstad

Wednesday 31 March 2004 1:36:59 am

The reason for this is that cookies does not work on different domains. So if you want to use both domain.com and www.domain.com you should use relative url's in your links, this should solve the problem. Then the user will always to linked to the current domain.

--bård

Documentation: http://ez.no/doc