Forums (Obsolete)

Member

eric-eaststaff - 10/29/2012 9:56:56 AM

Chat Cross-Domain

I'm using the Chat module with Kentico 6 and I'm having a hard time getting it to work.

Everything seems to be installed fine, and it works when accessing the site locally. When accessing it remotely I was getting a lot of errors, so I set the headers to allow all origins, set the allowed methods header, dealt with the OPTIONS verb, and managed to get rid of all of the errors.

Here's what's going on now: The staging sever is at http://mydomain:8007/chatpage. If I try to log in to chat it will log in and then immediately log out. No javascript errors, fiddler shows all OK, no errors it just fails. Now, if I go to http://www.mydomain:8007/chatpage it works just fine. Fiddler shows that when the chat service is accessed the host is mydomain:8007, not www.mydomain:8007. So it seems to be a problem with this being seen as cross-domain because of the www, but cross-domain access should be allowed.

In production, the situation is similar. The server is at mydomain:8008. If I access it with the URL mydomain:8008 it works fine, but if I use the public URL mydomain it doesn't work. Seems to be a cross-domain problem again, this time with the port number.

Any ideas what's going on here? I've spent tons of time googling cross-domain issues and trying every fix I can find. Now that I'm not getting any errors at all I don't have much to go on. I'm missing something somewhere, if you have any ideas please let me know.


Member	eric-eaststaff - 10/30/2012 11:11:01 AM RE:Chat Cross-Domain Update: The chat module itself seems to be working fine across domains, but as soon as it authenticates and logs in it immediately logs back out. I'm thinking that this is an issue with the domain on the authentication cookie, is there any way to change the domain name used for the authentication cookie? Where does this come from?

Member

eric-eaststaff - 10/31/2012 4:22:02 PM

RE:Chat Cross-Domain

Another update:

Now the workaround of adding the port number won't work, because when we edit the page layout and add a link with a port number (like http://mysite:8007/chatpage.aspx), it removes the port number on save and we're right back where we were, going to http://mysite/chatpage.aspx

Can we get some help on this? The chat page won't work without the port number and I can't get an answer on that, and now I see that the port number can't be put in the address because the editor is automatically removing it.

Kentico Support

kentico_jurajo - 11/5/2012 8:44:29 AM

RE:Chat Cross-Domain

Hi,

We have done some tests and we are unable to reproduce the issue. Could you please describe us in more details what you mean by staging server - are you using content staging or how the servers are configured?

Also, could you please tell us more details about the setup in the IIS for the www and non-www domain names together with the port numbers configuration so we can replicate your settings and reproduce the issue?

Thank you.

Best regards,
Juraj Ondrus

Member

eric-eaststaff - 11/5/2012 9:05:51 AM

RE:Chat Cross-Domain

Thanks for the response, and for looking into it. The deeper I get into this the more it looks like network issues on our end. The chat module itself seems to be working, it's the environment that seems to be causing problems (firewall, IIS config, etc.).

I talked to our network guy about this on Friday, and we decided that instead of trying to get this to work on the current web server it would be better to go ahead and move this site onto its own web server on port 80. I think that this will end our headaches with the port number, and we'd like to start breaking out our sites onto individual servers anyway.


Kentico Support	kentico_jurajo - 11/5/2012 9:11:23 AM RE:Chat Cross-Domain Thank you for the information. However, if you will have time in the future or you will find out something, we will appreciate if you would share it with us - here on forums for the community or we could add it e.g. to the documentation. Best regards, Juraj Ondrus