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.

URLs 404 when given a trailing slash /

See original GitHub issue

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

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

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:14 (9 by maintainers)

Top GitHub Comments

2reactions

trusktrcommented, Jun 8, 2020

I think we can default to README.md by matter of the existing conventions, and we can also fall back to index.md if README.md is not found. Thoughts? *#!/*JoePea

On 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.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docsifyjs/docsify/issues/1018#issuecomment-640803482, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACIVTW5D6WZPWFIKE3S7ADRVUWIXANCNFSM4KTDGRKQ .

1reaction

kosalanuwancommented, Jun 8, 2020

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.