Skip to content
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

Closed
aliams opened this issue Aug 16, 2016 · 6 comments
Closed

Add option to ignore case for cache querying #956

aliams opened this issue Aug 16, 2016 · 6 comments

Comments

@aliams
Copy link
Contributor

aliams commented Aug 16, 2016

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 in CacheQueryOptions?

@asutherland
Copy link

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.

@wanderview
Copy link
Member

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.

@jakearchibald
Copy link
Contributor

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.

@wanderview
Copy link
Member

A quick test in devtools shows that both firefox and chrome:

  1. Treat the origin of the URL as case insensitive
  2. Treat the path and query as case sensitive

In both browsers (1) seems to be implemented by normalizing the origin to lower case.

@annevk
Copy link
Member

annevk commented Aug 29, 2016

See the URL parser…

@jakearchibald
Copy link
Contributor

Notes:

  • Lowercase is tough to define
  • There are easy ways to work around this
  • We can reopen this if it turns out to be more difficult than we think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants