You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,11 +31,29 @@ Now, when a user which has not logged in yet opens the link to a file, he will b
31
31
32
32
Since version `2.3.0` you are also able to grant front end users access to the files in their user home directory in the settings of the member.
33
33
34
+
## Protect Resized Images
35
+
36
+
Since version `2.4.0` it is possible to also automatically protect any resized images (thumbnails) of protected files
37
+
which would otherwise be publicly available under `assets/images`. You can enable this feature in your config:
38
+
39
+
```yaml
40
+
# config/config.yaml
41
+
contao_file_access:
42
+
protect_resized_images: true
43
+
```
44
+
45
+
Note that this will however put additional load on your application as all requests to any resized protected image must
46
+
be processed by the application.
47
+
48
+
Also note that due to technical limitations you will always have access to these images (i.e. see these images) if you
49
+
are logged into the back end in your current browser session.
50
+
34
51
## Important Notes
35
52
36
53
Since this access restriction is done via PHP, the file is also sent to the client via PHP. This means that the `max_execution_time` needs to be sufficiently large, so that any file can be transferred to the client before the script is terminated. Thus you should be aware that problems can occur if a file is either very large or the client's connection to the server is very slow, or both. The script tries to disable the `max_execution_time`, though there is no guarantee that this will work. Also there can be other timeouts in the webserver.
37
54
38
-
Also currently any automatically generated images by Contao are __not__ protected. So if you use thumbnails of protected images, the URLs to these thumbnails can still be accessed by anyone. Though it is planned to also be able to protect those in a future version.
55
+
If you did not enable `protect_resized_images` (see above) and you use thumbnails of protected images, the URL to these
0 commit comments