Skip to content

Commit

Permalink
[DOC] Tpyos (bokeh#9211)
Browse files Browse the repository at this point in the history
  • Loading branch information
rs2 authored and bryevdv committed Sep 4, 2019
1 parent 05be3eb commit 8ce9a48
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions sphinx/source/docs/user_guide/server.rst
Original file line number Diff line number Diff line change
Expand Up @@ -652,8 +652,8 @@ can be found in the examples directory:
* :bokeh-tree:`examples/howto/server_embed/tornado_embed.py`

Also note that most every command line argument for ``bokeh serve`` has a
corresponding keyword argument to ``Server``. For instance setting the
--allow-sebsocket-origin`` command line argument is equivalent to passing
corresponding keyword argument to ``Server``. For instance, setting the
`--allow-websocket-origin` command line argument is equivalent to passing
``allow_websocket_origin`` as a parameter.

.. _userguide_server_bokeh_client:
Expand Down Expand Up @@ -1157,7 +1157,7 @@ instance, we typically want to restict the Bokeh server to honoring *only*
requests that originate from our ``acme.com`` page, so that other pages cannot
embed our Bokeh app without our knowledge.

This can be accomplished by setting the ``--allow-sebsocket-origin`` command
This can be accomplished by setting the ``--allow-websocket-origin`` command
line argument:

.. code-block:: sh
Expand All @@ -1174,7 +1174,7 @@ origin than ``acme.com``, and the Bokeh server will reject them.
determined and knowledgeble attacker can spoof Origin headers.

If multiple allowed origins are required, then multiple instances of
``--allow-sebsocket-origin`` can be passed on the command line.
``--allow-websocket-origin`` can be passed on the command line.

It is also possible to configure a Bokeh server to allow any and all connections
Regardless of origin:
Expand Down

0 comments on commit 8ce9a48

Please sign in to comment.