-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot download favicon for URLs #208
Comments
What exactly is the context of this? What to you mean with "download a favicon for any URL"? Edit: in general, JavaScript will not download data from any server at all as long as the server content Cross-Origin-Resource-Sharing policy (CORS) does not allow that. So the target server has to allow JavaScript loaded from other servers to access its data, which is usually never the case. |
@arnowelzel the function exists also if you use https://app.keeweb.info/. If you press this button here it should download the favicon from the website if it is available: So you say it is a CORS problem? How to fix it for a Nextcloud instance then? After downloading / pressing the button: On app.keeweb.info it works. |
I tried to reproduce the issue and got a CORS error about I put |
First, I just changed from
So, I added hmm. |
Successfully downloaded on another PC. |
@Slug-V it seems to be broken again but I think it is an error of the main app of keeweb because app.keeweb.info doesn't work either for me. Same for you? |
Mostly same.
it has an extremely slow loading, but worked for me. |
For me it does not work on app.keeweb.info either and I don't know how to fix that anyway and the upstream KeeWeb is not maintained any longer (also see #221). So sorry, I can not do anything about this. |
If I want to download a favicon for any URL in some entry I'll get:
Refused to load the image 'https://services.keeweb.info/favicon/mein.ionos.de' because it violates the following Content Security Policy directive: "img-src 'self' data: blob: https://favicon.keeweb.info".
And it is also telling:
It never worked. Does anybody have an idea how to fix this?
The text was updated successfully, but these errors were encountered: