-
Notifications
You must be signed in to change notification settings - Fork 313
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
Add option to ignore case for cache querying #956
Comments
Is the use-case for this web servers which are not (or whose backing file systems are not) case sensitive? If so, it would be great to know if their behavior is consistent with a single hard-coded unicode locale, a server-configurable unicode locale, etc. since that might allow the spec to standardize on a single interpretation versus specifying the collation to use for a given Cache at creation time. |
What do http cache impls do here? We could probably implement this without too much penalty. I'd like to see chrome implement it first, though. There are a number of cache query opts from v1 chrome still hasn't implemented. |
I don't want to do anything different to the HTTP cache in this regard, but I'm not sure what that is right now. |
A quick test in devtools shows that both firefox and chrome:
In both browsers (1) seems to be implemented by normalizing the origin to lower case. |
See the URL parser… |
Notes:
|
As a convenience for web developers, we should add an option to make querying from the cache case insensitive. Perhaps we should add an
ignoreCase
option inCacheQueryOptions
?The text was updated successfully, but these errors were encountered: