I'm concerned that our previewer is lying to users. If you go to a URL ending in / the previewer will add index.html onto the path for free. This makes the assumption that people have webservers that route / to index.html where they deploy the static files. This is not a good. Here are some possible fixes:
1. Don't have the previewer append index.html 2. Warn users whenever previewer does this in the logs. 3. Warn users whenever the previewer starts 4. Warn users on the website. 5. provide a command line option for explicitly making the previewer do the appending.
I think that I'm in favor of #5 it has the same correctness as #1 but is far less annoying.
I don't think it's weird to *have* a default document like this. I
think making user specify it manually each time would be annoying and
wouldn't match what you'd expect from a web server.
However, it's defiantly a good idea to allow users to configure it.
I'd be in favor of having some sensible defaults - namely index.html &
default.html (the defaults on apache & IIS) and allowing these to
added to configuration. This would be in line with what I would
expect from web servers.
okay, well if you are set on keeping it with defaults, I would say we need to at least mention this in some deploying section of the website, possibly we could provide a .htaccess file that explains how to do it, or at least provide the snippet of mod_rewrite code for apache.
I noticed there is some new config code on tdreyno's branch which seems nice. I guess we can put the DirectoryIndex configuration inside there.
On Thu, Jun 26, 2008 at 12:17 PM, Stephen Bartholomew <st...@curve21.com> wrote:
> I don't think it's weird to *have* a default document like this. I > think making user specify it manually each time would be annoying and > wouldn't match what you'd expect from a web server.
> However, it's defiantly a good idea to allow users to configure it. > I'd be in favor of having some sensible defaults - namely index.html & > default.html (the defaults on apache & IIS) and allowing these to > added to configuration. This would be in line with what I would > expect from web servers.
On Thu, Jun 26, 2008 at 1:56 PM, Ryan Mulligan <r...@ryantm.com> wrote: > okay, well if you are set on keeping it with defaults, I would say we need > to at least mention this in some deploying section of the website, possibly > we could provide a .htaccess file that explains how to do it, or at least > provide the snippet of mod_rewrite code for apache.
> I noticed there is some new config code on tdreyno's branch which seems > nice. I guess we can put the DirectoryIndex configuration inside there.
> On Thu, Jun 26, 2008 at 12:17 PM, Stephen Bartholomew <st...@curve21.com> > wrote:
>> Hey Ryan,
>> I don't think it's weird to *have* a default document like this. I >> think making user specify it manually each time would be annoying and >> wouldn't match what you'd expect from a web server.
>> However, it's defiantly a good idea to allow users to configure it. >> I'd be in favor of having some sensible defaults - namely index.html & >> default.html (the defaults on apache & IIS) and allowing these to >> added to configuration. This would be in line with what I would >> expect from web servers.
The problem with the previewer doing DirectoryIndexes is that if you deploy to somewhere that doesn't have DIrectoryIndices set up properly, your website, and links will be broken. This happened to me once, and I didn't notice right away because the previewer looked fine, but the deployed site had some broken links.
Ryan Mulligan
On Fri, Jun 27, 2008 at 10:16 AM, Stephen Bartholomew <st...@curve21.com> wrote:
> That's awesome - I'll check those all out shortly.
> However, I'm still not entirely clear why you're not keen on directory > indexes. What would you like to see coming up with you browse to the > previewer?
