Open MrDetonia opened 2 years ago
welcome[bot]
commented
2 years ago 👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
snipe
commented
2 years ago We do not ever hard code protocols into your urls, since we have no way of knowing whether you’re running TLS or not.
This is all dictated by your APP_URL in your .env
MoralCode
commented
1 year ago i had a similar issue where some styles were HTTP and others were HTTPS because my snipe install is behind a proxy and something got restarted causing the IP address i had set in APP_TRUSTED_PROXIES (link to docs) to be wrong.
WimSuenens
commented
1 year ago There's an extra space at the end in the link for the favicon.
<link rel="shortcut icon" type="image/ico" href="{{ ($snipeSettings) && ($snipeSettings->favicon!='') ? Storage::disk('public')->url(e($snipeSettings->favicon)) : config('app.url').'/favicon.ico' }} "> Could that be the issue?
Debug mode
Describe the bug
When using HTTPS, a custom favicon is requested over HTTP, resulting in the content being blocked by browsers due to mixed HTTPS/HTTP content.
Reproduction steps
Expected behavior
Favicon is requested in a schema that matches the one currently being used, e.g. HTTP when using HTTP, HTTPS when using HTTPS.
Screenshots
Snipe-IT Version
6.0.10
Operating System
Debian 11
Web Server
Apache
PHP Version
7.4.32
Operating System
Windows
Browser
Edge, Chrome, Brave
Version
Latest
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
Fresh install from Github. No Docker or container manager etc.