-
Notifications
You must be signed in to change notification settings - Fork 139
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
Consider defining "URL path" as a concept #792
Labels
editorial
Changes that do not affect how the standard is understood.
Comments
annevk
added
the
editorial
Changes that do not affect how the standard is understood.
label
Sep 25, 2023
annevk
changed the title
Considering defining "URL path" as a concept
Consider defining "URL path" as a concept
Sep 25, 2023
annevk
added a commit
that referenced
this issue
Jan 22, 2024
This will be useful for a future version of the Cookies RFC. Closes #792.
annevk
added a commit
that referenced
this issue
Jan 24, 2024
This will be useful for a future version of the Cookies RFC. Closes #792.
annevk
added a commit
that referenced
this issue
Jan 26, 2024
This will be useful for a future version of the Cookies RFC. Closes #792.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@johannhof and I have been looking at cookie layering, i.e., a refactoring of the Cookie RFC. One of the things that would be useful is to be able to refer to a URL path as its own concept, similar to how you can refer to a URL path segment today.
(I think we only need list-based URL paths, but it seems okay for the concept to encompass both. Perhaps other cookie clients want to support non-HTTP(S) schemes in some manner.)
The text was updated successfully, but these errors were encountered: