Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Nextcloud
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TeDomum
Nextcloud
Commits
fb5ac6b8
Commit
fb5ac6b8
authored
6 years ago
by
Oliver Wegner
Browse files
Options
Downloads
Patches
Plain Diff
Extending documentation in config.sample.php for `trusted_proxies`
Signed-off-by:
Oliver Wegner
<
void1976@gmail.com
>
parent
3eb5ac9c
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
config/config.sample.php
+18
-3
18 additions, 3 deletions
config/config.sample.php
with
18 additions
and
3 deletions
config/config.sample.php
+
18
−
3
View file @
fb5ac6b8
...
@@ -1499,11 +1499,26 @@ $CONFIG = array(
...
@@ -1499,11 +1499,26 @@ $CONFIG = array(
/**
/**
* List of trusted proxy servers
* List of trusted proxy servers
*
*
* If you configure these also consider setting `forwarded_for_headers` which
* You may set this to an array containing a combination of
* otherwise defaults to `HTTP_X_FORWARDED_FOR` (the `X-Forwarded-For` header).
* - IPv4 addresses, e.g. `192.168.2.123`
* - IPv4 ranges in CIDR notation, e.g. `192.168.2.0/24`
* - IPv6 addresses, e.g. `fd9e:21a7:a92c:2323::1`
*
* _(CIDR notation for IPv6 is currently work in progress and thus not
* available as of yet)_
*
* When an incoming request's `REMOTE_ADDR` matches any of the IP addresses
* specified here, it is assumed to be a proxy instead of a client. Thus, the
* client IP will be read from the HTTP header specified in
* `forwarded_for_headers` instead of from `REMOTE_ADDR`.
*
* So if you configure `trusted_proxies`, also consider setting
* `forwarded_for_headers` which otherwise defaults to `HTTP_X_FORWARDED_FOR`
* (the `X-Forwarded-For` header).
*
* Defaults to an empty array.
* Defaults to an empty array.
*/
*/
'trusted_proxies'
=>
array
(
'203.0.113.45'
,
'198.51.100.128'
),
'trusted_proxies'
=>
array
(
'203.0.113.45'
,
'198.51.100.128'
,
'192.168.2.0/24'
),
/**
/**
* Headers that should be trusted as client IP address in combination with
* Headers that should be trusted as client IP address in combination with
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment