Skip to content

docs: clarify hostname route matching includes the port #10568

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.

Sign up for GitHub

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

Open
gr8man wants to merge 1 commit into
base: develop
Choose a base branch
from
+9 −0
Open

docs: clarify hostname route matching includes the port #10568

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions user_guide_src/source/incoming/routing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -476,6 +476,15 @@ by passing the "hostname" option along with the desired domain to allow it on as
This example would only allow the specified hosts to work if the domain exactly matched **accounts.example.com**.
It would not work under the main site at **example.com**.

.. note::

The ``hostname`` option is compared against the full ``HTTP_HOST`` value of the
request, including the port when one is present. When your application is served
on a non-standard port (for example ``localhost:8080``, behind Docker, or when
using ``php spark serve``), you must include the port in the ``hostname`` option for
the routes to match. For example, ``['hostname' => 'localhost:8080']`` matches only
requests to ``localhost:8080``.

Restrict by Multiple Hostnames
------------------------------

Expand Down