minor #13737 [HttpFoundation] Fix getHost and getPort functions in docblock (jwpage)
This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #13737).
Discussion
----------
[HttpFoundation] Fix getHost and getPort functions in docblock
This fixes the incorrect references to the functions `getClientHost` and `getClientPort` in the docblock for Request::setTrustedHeaderName.
| Q | A
| ------------- | ---
| Fixed tickets | none
| License | MIT
Commits
-------
1ae9f9c
[HttpFoundation] Fix getHost and getPort functions in docblock
This commit is contained in:
commit
19aa6dcf65
@ -575,8 +575,8 @@ class Request
|
|||||||
* The following header keys are supported:
|
* The following header keys are supported:
|
||||||
*
|
*
|
||||||
* * Request::HEADER_CLIENT_IP: defaults to X-Forwarded-For (see getClientIp())
|
* * Request::HEADER_CLIENT_IP: defaults to X-Forwarded-For (see getClientIp())
|
||||||
* * Request::HEADER_CLIENT_HOST: defaults to X-Forwarded-Host (see getClientHost())
|
* * Request::HEADER_CLIENT_HOST: defaults to X-Forwarded-Host (see getHost())
|
||||||
* * Request::HEADER_CLIENT_PORT: defaults to X-Forwarded-Port (see getClientPort())
|
* * Request::HEADER_CLIENT_PORT: defaults to X-Forwarded-Port (see getPort())
|
||||||
* * Request::HEADER_CLIENT_PROTO: defaults to X-Forwarded-Proto (see getScheme() and isSecure())
|
* * Request::HEADER_CLIENT_PROTO: defaults to X-Forwarded-Proto (see getScheme() and isSecure())
|
||||||
*
|
*
|
||||||
* Setting an empty value allows to disable the trusted header for the given key.
|
* Setting an empty value allows to disable the trusted header for the given key.
|
||||||
|
Reference in New Issue
Block a user