-
Notifications
You must be signed in to change notification settings - Fork 1
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
The migration test server breaks rather frequently on resources ending with /
#76
Comments
@michielbdejong
|
401 for /settings/test.html is wrong and should succeed with 200. |
Yes, that is what we wanted, right? If a URL is inaccessible and it has no slash, then Pivot redirects the user to that URL but with the slash. This was one of the first feature requests, see #4 We discussed doing it only if the container exists, but thought that that would be leaking information. So yes, if https://pod.com/foo is a 401, a 403, or a 404 for the user, then we redirect to https://pod.com/foo/ Is the behaviour not what we want? Maybe we only want to do it in case of a 404, for instance? |
With the actual code the only solution is to only check for Personally I think we should have had something like. If URL ends with('/') don't do anything => return The 200 may cover 2xx and may be 304 ??? |
I'm seeing errors in the log like this one:
These probably come from the fact that there is no try-catch around this code. I'll see what happens when I add a try-catch there. |
see details here CommunitySolidServer/Recipes#45
The logs show 2 different issues on on locks and one on
/
Could Pivot be responsible for the
7
one ?The text was updated successfully, but these errors were encountered: