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

Use domain instead of port in docs (#539)

Browse Source
This commit is contained in:
Hassen ben tanfous 2017-02-21 00:11:28 +01:00 committed by Andrew Godwin
parent 7625ed2700
commit db3a020122
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/deploying.rst
View File

@ -144,7 +144,7 @@ and configure routing in front of your interface and WSGI servers to route
requests appropriately.
If you use Daphne for all traffic, it auto-negotiates between HTTP and WebSocket,
so there's no need to have your WebSockets on a separate port or path (and
so there's no need to have your WebSockets on a separate domain or path (and
they'll be able to share cookies with your normal view code, which isn't
possible if you separate by domain rather than path).

2
docs/getting-started.rst
View File

@ -492,7 +492,7 @@ chat to people with the same first letter of their username::
If you're just using ``runserver`` (and so Daphne), you can just connect
and your cookies should transfer your auth over. If you were running WebSockets
on a separate port, you'd have to remember to provide the
on a separate domain, you'd have to remember to provide the
Django session ID as part of the URL, like this::
socket = new WebSocket("ws://127.0.0.1:9000/?session_key=abcdefg");