-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Case-insensitive option #92
Comments
As expected, this breaks Linux systems running sirv without caching enabled. My initial impression is that this may be too fussy to accommodate |
Without caching the implementation is a file probe, which is dependent on OS semantic (e.g. case-insensitive on Win, case-sensitive on Linux). I agree that trying to change the OS semantics is a serious hassle. What about just having an option to configure the cached behaviour? It's not perfect as one cannot change the OS semantics without cache, but it's a nice improvement. |
How about options.insensitive or options.lowercase |
yeah it would do the job. |
Is it possible to add an option to make sirv case-insensitive?
That would probably mean making the normalized path lowercase in
FILES
and doing the same on incoming path.Motivation
Currently on Windows sirv behaves differently in dev mode vs not, because in dev mode every request is a file system check, which is case-insensitive on Win.
When you run the same folder from sirv static cache, it becomes case-sensitive and some requests suddenly fail.
Also it is common for some (but not all) web servers to be case-insensitive.
The text was updated successfully, but these errors were encountered: