-
Notifications
You must be signed in to change notification settings - Fork 683
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
Support foo/index.html -> foo/ without stripping ".html" from other paths? #431
Comments
I second this. Prefer old default behavior better. |
To phrase the issue a little more generally, I think the latest release has introduced some disconnect between the stated purpose of the package and its functionality:
This description (especially the first paragraph) makes I realize consistency within the Zeit ecosystem is important, and it's something I value about Zeit, so if this is all intended behavior I'll certainly understand. But in that case I think the language in the readme describes this package as being more general-purpose than it is today. |
We modeled |
With Superstatic's implementation of |
I'd like to second this as well. The behavior behind cleanUrls is unintuitive and breaks relative paths within directories of static HTML files, i.e. whenever one document links to |
yes, my plain html file is getting broken. |
The standard behavior I'm used to from a static file serving program is that
foo.html
should be served as-is, but requests forfoo/
should servefoo/index.html
if it exists, rather than a directory listing. The newcleanUrls=false
setting lets me preventfoo.html
from redirecting tofoo
, but also loses the ability to servefoo/
.Are these two things intentionally part of the same setting? I'm not sure how to get back to a traditional behavior here. Thanks!
cleanUrls=true
cleanUrls=false
I would prefer:
The text was updated successfully, but these errors were encountered: