Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pathnames are case sensitive
See original GitHub issue/learn is not the same as /LEARN or /LeArN. The second two take you to user profiles, I believe they are the same user profiles. Just starting an issue about it, I haven’t looked into it at all.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
File paths in Windows environment not case sensitive?
Yes. Windows (local) file systems, including NTFS, as well as FAT and variants, are case insensitive (normally).
Read more >Adjust case sensitivity - WSL - Microsoft Learn
Case sensitivity determines whether uppercase (FOO.txt) and lowercase (foo.txt) letters are handled as distinct (case-sensitive) or ...
Read more >How to Enable Case Sensitive File and Folder Names on ...
This feature is enabled via the fsutil.exe command, which you must run from the command line. You can do it from either a...
Read more >path/filepath: Glob is case-sensitive on Windows · Issue #5441
1rc3 windows/386 File paths on Windows are normally case-insensitive, but the filepath.Glob is currently case-sensitive on Windows. I would expect it to be...
Read more >Case-sensitivity of file and directory names in a multiprotocol ...
On NFS clients, you see both directory names as they were created, for example testdir and TESTDIR , because directory names are case-sensitive....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We will not be using
/u/usernamepattern, there are a lot of backlinks that will be broken.We also reserve the right to claim a path for our use as needed. Its on the user’s part to NOT choose that is something unconventional.
Practically why would you choose a username ‘LEARN’?
We have claimed paths in the past, by sending a notification to users for the change.
That said, this is a valid issue, we should add a middleware to make paths case-insentive. I am not sure yet, but this would mean the change can be at the client level as well, in addition to the API separately.
@thecodingaviator if we can do that, it would simplify the client code and cut down on the number of unavoidable 404s. Mrugesh will know if there’s a reason not to beyond “it’ll be a complicated rewrite”.