docsify: URLs 404 when given a trailing slash /
Bug Report
Steps to reproduce
Go to any page path and add a trailing slash / to the end
Example: /#/hello/
What is current behaviour
The page apth /#/hello/ will 404
What is the expected behaviour
That the page requested is shown and works the same as /#/hello
Other relevant information
No
-
Bug does still occur when all/other plugins are disabled?
-
Your OS: Windows 10
-
Node.js version: 8.11.3
-
npm/yarn version: 5.6.0
-
Browser version: Chrome Version 79.0.3945.130
-
Docsify version: latest unpkg (4.10.2)
-
Docsify plugins: search
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 2
- Comments: 15 (10 by maintainers)
This is is annoying for sure. We need to handle trailing slashes properly.
Additionally, we have high-level things to improve in Docsify:
I think we can default to
README.mdby matter of the existing conventions, and we can also fall back toindex.mdifREADME.mdis not found. Thoughts? *#!/*JoePeaOn Mon, Jun 8, 2020 at 11:42 AM Kosala Nuwan Perera < notifications@github.com> wrote:
In GitHub Pages, isn’t README.md is the index.html or default.html behavior? I mean it would make more sense to have a README.md as a convention.
Whoa, I’m two years late to the party, but has this been resolved at all? It’d be terrific if
example.org/hello/READMEwas just the same asexample.org/helloI have not started work on this. Will give it a crack over the weekend. Help is welcome should anyone else find they have the time.