GitLab 11.4.3 "Outbound requests" setting path
This commit is contained in:
parent
b5a79f1536
commit
744759e404
1 changed files with 1 additions and 1 deletions
|
@ -12,7 +12,7 @@ If a web service does not require authentication, Webhooks can be used to trigge
|
||||||
|
|
||||||
To prevent this type of exploitation from happening, starting with GitLab 10.6, all Webhook requests to the current GitLab instance server address and/or in a private network will be forbidden by default. That means that all requests made to 127.0.0.1, ::1 and 0.0.0.0, as well as IPv4 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and IPv6 site-local (ffc0::/10) addresses won't be allowed.
|
To prevent this type of exploitation from happening, starting with GitLab 10.6, all Webhook requests to the current GitLab instance server address and/or in a private network will be forbidden by default. That means that all requests made to 127.0.0.1, ::1 and 0.0.0.0, as well as IPv4 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and IPv6 site-local (ffc0::/10) addresses won't be allowed.
|
||||||
|
|
||||||
This behavior can be overridden by enabling the option *"Allow requests to the local network from hooks and services"* in the *"Outbound requests"* section inside the Admin area under **Settings** (`/admin/application_settings`):
|
This behavior can be overridden by enabling the option *"Allow requests to the local network from hooks and services"* in the *"Outbound requests"* section inside the Admin area under **Settings** (`/admin/application_settings/network`):
|
||||||
|
|
||||||
![Outbound requests admin settings](img/outbound_requests_section.png)
|
![Outbound requests admin settings](img/outbound_requests_section.png)
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue