@@ -176,7 +176,7 @@ pattern so that it is only accessible by requests from the local server itself:
176176 # ...
177177 access_control :
178178 #
179- - { path: ^/internal, roles: IS_AUTHENTICATED_ANONYMOUSLY, ips: [127.0.0.1, fe80::1, ::1] }
179+ - { path: ^/internal, roles: IS_AUTHENTICATED_ANONYMOUSLY, ips: [127.0.0.1, ::1] }
180180 - { path: ^/internal, roles: ROLE_NO_ACCESS }
181181
182182 .. code-block :: xml
@@ -193,7 +193,7 @@ pattern so that it is only accessible by requests from the local server itself:
193193 <!-- ... -->
194194 <rule path =" ^/internal"
195195 role =" IS_AUTHENTICATED_ANONYMOUSLY"
196- ips =" 127.0.0.1, fe80::1, ::1"
196+ ips =" 127.0.0.1, ::1"
197197 />
198198
199199 <rule path =" ^/internal" role =" ROLE_NO_ACCESS" />
@@ -209,7 +209,7 @@ pattern so that it is only accessible by requests from the local server itself:
209209 array(
210210 'path' => '^/internal',
211211 'role' => 'IS_AUTHENTICATED_ANONYMOUSLY',
212- 'ips' => '127.0.0.1, fe80::1, ::1'
212+ 'ips' => '127.0.0.1, ::1'
213213 ),
214214 array(
215215 'path' => '^/internal',
@@ -230,8 +230,8 @@ the external IP address ``10.0.0.1``:
230230 that does not match an existing role, it just serves as a trick to always
231231 deny access).
232232
233- But if the same request comes from ``127.0.0.1 ``, ``::1 `` (the IPv6 loopback
234- address) or `` fe80::1 `` (the IPv6 link-local address) :
233+ But if the same request comes from ``127.0.0.1 `` or ``::1 `` (the IPv6 loopback
234+ address):
235235
236236* Now, the first access control rule is enabled as both the ``path `` and the
237237 ``ip `` match: access is allowed as the user always has the
0 commit comments