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

/favicon.ico returns 406 #7810

Closed
garethrees opened this issue Jul 4, 2023 · 3 comments · Fixed by #7816
Closed

/favicon.ico returns 406 #7810

garethrees opened this issue Jul 4, 2023 · 3 comments · Fixed by #7816
Labels
bug Breaks expected functionality f:framework x:uk

Comments

@garethrees
Copy link
Member

$ curl --silent -I https://www.whatdotheyknow.com/favicon.ico | head -n 1
HTTP/2 406

The favicon is rendered, but via an asset URL with digest, e.g.:

<link rel="icon" type="image/x-icon" href="/assets/favicon-afe76651f859e6a7b6b153def0358ae1b959842c02fdc46bc3adca58eb6395b2.ico" />

Not just mySociety-hosted installs, so probably an issue in Alaveteli somewhere:

$ curl --silent -I https://madada.fr/favicon.ico | head -n 1
HTTP/1.1 406 Not Acceptable

Might be an issue with the symlinking non-digest asset task.

@garethrees garethrees added x:uk bug Breaks expected functionality f:framework labels Jul 4, 2023
@gbp
Copy link
Member

gbp commented Jul 6, 2023

This is due to some browsers on respecting the link tag in the HTML page header. The favicon is at /assets/favicon.ico. I have added an Apache rewrite rule to handled these.

@gbp gbp closed this as completed Jul 6, 2023
@garethrees
Copy link
Member Author

Presumably this fixes it just for us? Should Alaveteli come with an update to config/httpd.conf-example?

@gbp
Copy link
Member

gbp commented Jul 7, 2023

Ooh I will have to test this.

Linking to my comment on how to do this in UTM as it took me ages to find this:
#7503 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Breaks expected functionality f:framework x:uk
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants