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

Outline.expand error, Fetcher: <https://solidweb.org/profile/card> status: 403 #178

Closed
chunt007 opened this issue Jul 29, 2022 · 9 comments
Labels
wontfix This will not be worked on

Comments

@chunt007
Copy link

This error occurs when you are simply going to Solid Profile Card

By default with no user logged in. Even if the browser is completely clear and anything cached is erased, it still appears.

403
outlinexpand

@jeff-zucker
Copy link
Collaborator

It says it is trying to open <https://solidweb.org/profile/card> which is not your WebID - there's no username.

@jeff-zucker
Copy link
Collaborator

So that means that the "oops couldn't find out who you are" was exactly the right response.

@jeff-zucker
Copy link
Collaborator

The reason the 401 error is shown is that the public does not have read access to the server root, only on specific files like index.html. There is, AFAIK, no such container as https://soldiweb.org/profile/ (@ewingson can you confirm). You might think that you would get a 404 but it is a general security practice to not show 404s in protected containers - if you don't have right to read the container, you don't have the right to know if a particular resource is contained in it or not, so you don't see the 404.

@chunt007
Copy link
Author

You just worded what I suspected @jeff-zucker. This outline.expand error also appears in two of my broken pod accounts. I was going to say that 404's are handled differently on other sites. They usually don't show scripting exceptions.

@jeff-zucker
Copy link
Collaborator

Yeah, I'm not sure exactly which servers implement the no-404 policy.

@jeff-zucker
Copy link
Collaborator

Outline-expand errors can be caused by many things, not just this. Some are justified, some may be bugs.

@ewingson
Copy link
Member

I can confirm there is no https://solidweb.org/profile container that I am aware of without the username as subdomain.
however, trying to access this URI per browser gives a 401 not logged in and a 403 logged in.

@jeff-zucker
Copy link
Collaborator

@ewingson - that's exactly what I'd expect - the 401/403 trumps 404 and should be displayed instead so as to not divulge information about what the protected server root contains.

@timea-solid
Copy link
Member

This was occurring because the profile got to be very very big and could not load.
This is related to another bug - duplicate entries of trustedApps. SolidOS/solid-ui#473

@timea-solid timea-solid added the wontfix This will not be worked on label Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants