You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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:
@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: