django/daphne
1
1
Fork 0
mirror of https://github.com/django/daphne.git synced 2025-04-20 16:52:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

use domain instead of port (#537)

Browse Source 
i think this is a typo, as cookies aren't restricted by port, so even if you offload on the same domain, daphne will still work without having to specify a ``session_key`` GET parameter since it can read the django session cookie which it defaults to.
This commit is contained in:
Hassen ben tanfous 2017-02-20 01:16:37 +01:00 committed by Andrew Godwin
parent 672de2b2a3
commit 7625ed2700
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/getting-started.rst
View File

@ -439,10 +439,10 @@ both authentication and getting the underlying Django session (which is what
Django authentication relies on).
Channels can use Django sessions either from cookies (if you're running your
websocket server on the same port as your main site, using something like Daphne),
websocket server on the same domain as your main site, using something like Daphne),
or from a ``session_key`` GET parameter, which works if you want to keep
running your HTTP requests through a WSGI server and offload WebSockets to a
second server process on another port.
second server process on another domain.
You get access to a user's normal Django session using the ``http_session``
decorator - that gives you a ``message.http_session`` attribute that behaves