@@ -24,7 +24,7 @@ $tokenAuthentication = new TokenAuthentication(
24
24
Sign a URL.
25
25
26
26
``` php
27
- // Root directory.
27
+ // File in root directory.
28
28
$tokenAuthentication->sign(
29
29
file: '/bunny.jpg',
30
30
expirationTime: 3600,
@@ -38,7 +38,7 @@ $tokenAuthentication->sign(
38
38
allowSubnet: true
39
39
);
40
40
41
- // Subdirectory .
41
+ // File in subdirectory .
42
42
$tokenAuthentication->sign(
43
43
file: '/css/custom.css',
44
44
);
@@ -101,8 +101,8 @@ $tokenAuthentication->sign(
101
101
- In order to reduce the false negatives (and increase privacy) for Token IP validation, the default is to
102
102
allow the full `/24` subnet. As an example, a token signed for a user with IPv4 `12.345.67.89` will allow
103
103
`12.345.67.0/24` to access the resource.
104
- - The `countriesAllowed`, `countriesBlocked` and `countriesBlocked ` accept comma separated input. This means
105
- you could allow or block multiple countries like so: `US,DE,JP`. Same goes for referers: `example.com,example.org`.
104
+ - The arguments `countriesAllowed`, `countriesBlocked` and `referrersAllowed ` accept comma separated input. This means
105
+ you could allow or block multiple countries like so: `US,DE,JP`. Same goes for the allowed referers: `example.com,example.org`.
106
106
- An edge case occurs when you add a blocked country to the Traffic Manager, and allow that same country for
107
107
token authentication. This will result in a standard **"Unable to connect"** page. According to support *"The reason for
108
108
that would be is due to the fact that the Traffic manager doesn't resolve
0 commit comments