Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding support to cross domains. #185

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

Conversation

yguarata
Copy link
Contributor

It was added the setting WEBSOCKET_HOST. This enables using websockets in cross domains. This is, the websocket domain (e.g. ws.myapp.com) is different from the site domain (e.g. www.myapp.com). However, it is mandatory to provide the Django setting SESSION_COOKIE_DOMAIN (e.g. SESSION_COOKIE_DOMAIN = '.myapp.com'). This pull request is backwards compatible. Documentation and changelog were updated accordingly.

@@ -6,6 +6,11 @@ Release History

0.4.7 develop
-------------

Instalation settings:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Installation Settings*

@jrief
Copy link
Owner

jrief commented Apr 6, 2017

please rebase your pull request

yguarata added 7 commits July 13, 2017 15:52
The setting WEBSOCKET_HOST enables using Websockets in cross domains. This is, the websocket domain (e.g. ws.myapp.com) is different from the site domain (e.g. www.myapp.com). However, it is mandatory to provide the Django setting SESSION_COOKIE_DOMAIN (e.g. SESSION_COOKIE_DOMAIN = '.myapp.com').
The setting WEBSOCKET_HOST enables using Websockets in cross domains. This is, the websocket domain (e.g. ws.myapp.com) is different from the site domain (e.g. www.myapp.com). However, it is mandatory to provide the Django setting SESSION_COOKIE_DOMAIN (e.g. SESSION_COOKIE_DOMAIN = '.myapp.com').
The setting WEBSOCKET_HOST enables using Websockets in cross domains. This is, the websocket domain (e.g. ws.myapp.com) is different from the site domain (e.g. www.myapp.com). However, it is mandatory to provide the Django setting SESSION_COOKIE_DOMAIN (e.g. SESSION_COOKIE_DOMAIN = '.myapp.com').
Adding cross domain support.
@yguarata
Copy link
Contributor Author

Pull request rebased.

@yguarata
Copy link
Contributor Author

Closing this pull request because it is a little bit out of sync. I will perform some tests before opening another pull request.

@yguarata yguarata closed this Jul 14, 2017
@yguarata yguarata reopened this Jul 17, 2017
@yguarata
Copy link
Contributor Author

I've tested it with Django 1.8.18 and 1.11.3.
Did I miss anything?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants