| Summary: | url filter blockpage backround won't show | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Arne.F <arne.fitzenreiter> |
| Component: | --- | Assignee: | Peter Müller <peter.mueller> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Aesthetic Issue | ||
| Priority: | Will affect an average number of users | CC: | bbitsch, michael.tremer |
| Version: | 2 | ||
| Hardware: | all | ||
| OS: | All | ||
|
Description
Arne.F
2018-02-27 22:05:55 UTC
(In reply to Arne Fitzenreiter from comment #0) > The background image will not displayed because content security policy will > block loading images from ipfire. Correctly, I have not thought about that. > > the image should whitelisted or embedded into the blockpage. Whitelisting is probably difficult since we don't know the IPFire's address or domain name. Embedding the image into the page itself might be an option, but I think this is tricky with larger images (embedded PNG data?). Is disabling Content-Security-Policy on port 81 an option? Are there any other services than the squid's error pages? Update accellerator is running on the same port and delivering basically untrusted content. So I would say embedding is the best option. CSS allows to embed pretty much anything when it is encoded in base64. It isn't too great of a solution since we have to deliver the image every time and it will never be cached locally. But security comes first and we are serving this in a local network most of the time which should have the bandwidth. Okay. Currently, I do not know much about embedding in CSS yet, but I'll have a look. Sent in second patch: https://patchwork.ipfire.org/patch/1846/ Sent in third patch (which actually works!): https://patchwork.ipfire.org/patch/1903/ |