-
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
Display containers even if trailing slash is missing from the URL #4
Comments
CSS' issue on this topic, seems that there is no conflict ( neither obligation ) from the spec perspective, and it could be merged upstream |
The patch only works when logged-in, else fails with 401 unauthorized |
Also note - I tested /public and it redirected me to /public/ correctly BUT it did not add the trailing slash to the browser location bar URI. NSS does add the slash to the URI. |
I found this behavior
|
Ah, good catch! I guess in that case our code is not reached. I'll fix that.
I'll look into that as well! Maybe that's a subtle difference between a 301 and a 302 or something. |
I have to look at CSS architecture and see where we can do the check for public resources. |
Testing this with https://michielbdejong.pivot.pondersource.com/README/ |
As noted in #29 it's probably better to find a different point in the architecture to address this issue, and then fix it once and for all for both publish and non-public resources, and without confusing the DPoP checker and the locking mechanism. |
Maybe the best place to do this is actually in mashlib: |
No description provided.
The text was updated successfully, but these errors were encountered: