diff --git a/doc/settings/configuration.md b/doc/settings/configuration.md
index c738f995e477fd7d3fa7ade5a2c850c5973f28c4_ZG9jL3NldHRpbmdzL2NvbmZpZ3VyYXRpb24ubWQ=..8e0fad4f9dcd4aa22382da390b0ec64fed65835f_ZG9jL3NldHRpbmdzL2NvbmZpZ3VyYXRpb24ubWQ= 100644
--- a/doc/settings/configuration.md
+++ b/doc/settings/configuration.md
@@ -706,6 +706,6 @@
 There are no known security issues in GitLab caused by not configuring `allowed_hosts`,
 but it's recommended for defense in depth against potential [HTTP Host header attacks](https://portswigger.net/web-security/host-header).
 
-If using a custom external proxy such as apache, it may be necessary to add the localhost. Administrators should add filters to the external proxy to mitigate potential HTTP Host header attacks passed through the proxy to workhorse.
+If using a custom external proxy such as Apache, it may be necessary to add the localhost address or name (`localhost` or `127.0.0.1`). You should add filters to the external proxy to mitigate potential HTTP Host header attacks passed through the proxy to workhorse.
 
 ```ruby
@@ -710,6 +710,6 @@
 
 ```ruby
-gitlab_rails['allowed_hosts'] = ['gitlab.example.com', '127.0.0.1']
+gitlab_rails['allowed_hosts'] = ['gitlab.example.com', '127.0.0.1', 'localhost']
 ```
 
 ## Related topics