Skip to content
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

Blacksmith should not assume index.html completion #18

Open
jfhbrook opened this issue Dec 5, 2011 · 1 comment
Open

Blacksmith should not assume index.html completion #18

jfhbrook opened this issue Dec 5, 2011 · 1 comment

Comments

@jfhbrook
Copy link
Contributor

jfhbrook commented Dec 5, 2011

Quote from Bradley:

Currently we assume index.html completion for servers, which while using Apache, node-http-server, etc. is viable, pushing content to a CDN for static sites is a common solution that may not support directory forwarding to index.html.

I'm not actually sure what needs to change in blacksmith to allow for this use case.

@keithgutfreund
Copy link

I think the problem is that the hrefs created by Blacksmith are not terminated by slashes. For example, this is an href created by Blacksmith:
href="/research-agenda">research agenda
Apache is smart enough to first look for a file called "/research-agenda" and when that fails it next looks for "/research-agenda/index.html" which succeeds. Unfortunately, nginx, for example, does not do this and fails to find research-agenda/index.html. So, in these cases the hrefs created by Blacksmith should be terminated by slashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants