cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Reopened] (COCOON-2326) Confusing/messy index listings on mirrors
Date Tue, 07 Aug 2012 16:31:10 GMT


Sebb reopened COCOON-2326:


Unfortunately it looks like there was a faulty temporary version of the file that was picked
up by several mirrors.
This caused the cocoon directory to be inaccessible.

Hopefully they will pick up the corrected version within the next 24hrs maximum.

The file still contains an IndexOptions entry. 
Although this is currently the same as the recommended mirror settings, it is redundant.
Also if the default settings were ever changed, your htaccess file would also need changing.

It's best not to override the IndexOptions, but if there is a genuine need to change them
just for Cocoon, then it would be better to use the + or - qualifiers to override the inherited
settings as needed, see:
> Confusing/messy index listings on mirrors
> -----------------------------------------
>                 Key: COCOON-2326
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Documentation
>            Reporter: Sebb
>            Assignee: Francesco Chicchiriccò
> The distribution directories use customised .htaccess files to change the look of the
generated index listings.
> However, the IndexOptions settings do not agree with the standard settings used elsewhere
and which are required for our mirrors [1].
> In particular, FoldersFirst and ScanHTMLTitles are missing.
> This is potentially confusing for users.
> Removing the IndexOptions entry from .htaccess would solve the issue.
> Also, the .htaccess files override the images used for folders and file types.
> However, these use relative links, and only currently work for directories that contain
the appropriate .htaccess file.
> So for example the following index listing looks very messy:
> It's also potentially confusing for mirror users to see different icons for the same
file types in different Apache products.
> Again, removing the entries would be one way to solve the issue.
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message