Skip to content
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

404 on https://nodejs.org/static/images/favicons/favicon.ico #7413

Open
legendecas opened this issue Jan 21, 2025 · 3 comments
Open

404 on https://nodejs.org/static/images/favicons/favicon.ico #7413

legendecas opened this issue Jan 21, 2025 · 3 comments
Labels

Comments

@legendecas
Copy link
Member

URL:

https://nodejs.org/static/images/favicons/favicon.ico

Browser Name:

Browser Version:

Operating System:

How to reproduce the issue:

The favicon is referenced at https://github.com/nodejs/node/blob/7bc2946293757389468f1fa09714860f8e1147b7/src/inspector_socket_server.cc#L350 on the Chrome devtools page.

@legendecas legendecas added the bug label Jan 21, 2025
@legendecas
Copy link
Member Author

Taking this together with #7382, it will be nice if there are sort of permalinks for these resource files.

@AugustinMauroy
Copy link
Member

AugustinMauroy commented Jan 21, 2025

I understand your pain point. But for node core thing why not use GH raw ping on commit ?

@legendecas
Copy link
Member Author

GitHub raw content domain should work... but why not https://nodejs.org? It feels odd to avoid linking to the website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants