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

MWS: Anonymous access to favicon is broken #8832

Open
Jermolene opened this issue Dec 20, 2024 · 2 comments
Open

MWS: Anonymous access to favicon is broken #8832

Jermolene opened this issue Dec 20, 2024 · 2 comments

Comments

@Jermolene
Copy link
Member

This bug was encountered with the commit e48ea2d.

Steps to reproduce:

  1. Make a fresh install of MWS
  2. Run npm install and npm start
  3. Open localhost:8080 in a browser and observe that the favicons are not displayed correctly
  4. In developer tools, observe that the server is returning 401 for the favicons, despite anonymous access being enabled
image

cc @webplusai

@Jermolene
Copy link
Member Author

On further investigation it turns out that access to the wikis themselves is also blocked with 401. So I think anonymous access might be substantially broken.

@pmario
Copy link
Member

pmario commented Dec 20, 2024

@Jermolene -- Do you have "access right hierarchy" in mind. From my point of view it is a bit "out of control" at the moment. I know there is a bit of Specification /Reference at the mws docs, but from my point of view that's not specific enough to create a working system out of it.

We do have experience from TiddlySpace, which IMO worked quite well.
You also have a lot of experience with the Anna Freud Center -- From there you should know, what is "good enough" and what is "missing".

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

No branches or pull requests

2 participants