You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Martin Kraemer <Ma...@mch.sni.de> on 1997/09/18 09:37:32 UTC

mod_autoindex (was: Year 2000 Compliance)

Not quite so. Internally, of course it is compliant. On protocol level,
too. On the user level, however, not 100% (yet). Think of the mod_autoindex
directory listings: They display the modification dates as...

    apache_1.3a1.tar.gz    23-Jul-97 02:23   792k  WinNT-Apache-1.3Alpha
    apache_1.3b1-19970915..15-Sep-97 09:01   864k
				  ^^
That's a 2-digit-year allright. But I was thinking of fumbling with
mod_autoindex anyway, why not fix that as well. ;-)

What mod_autoindex needs IMO is

*   The width of the File Column and Description Column ought to be
    user-definable, I was thinking of new
	IndexOptions   FileColumnWidth=nnn DescColumnWidth=nnn

*   The date should be Y2kC (Year2000Compliant) -or at least
    programmable (strftime comes to mind).  But a new parser for, e.g.,
	IndexOptions   DateFormat="%d. %B %Y"  DateColumnWidth=17
    would influence other core sources like http_config.c as well.

*   general cleanup: a char* and a bitmask are used interchangeably for
    the same purpose; unless the actual address of the pointer can be
    guaranteed not to conflict with any possible bit combination, this
    invites trouble.

*   general cleanup: prohibit invalid options like
	IndexOptions IconHeightIsAValidKeywordButThisShouldntBe

    Martin

On Wed, Sep 17, 1997 at 09:54:10PM -0700, Alexei Kosut wrote:
> On Wed, 17 Sep 1997, Brian Behlendorf wrote:
> 
> > Don't laugh.  
> > 
> > What does it take to be certified as Y2K compliant?
> 
> Dunno. But Apache is definitely compliant.
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: mod_autoindex (was: Year 2000 Compliance)

Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Thu, Sep 18, 1997 at 01:47:41AM -0700, Dean Gaudet wrote:
> >     [...] But a new parser for, e.g.,
> > 	IndexOptions   DateFormat="%d. %B %Y"  DateColumnWidth=17
> >     would influence other core sources like http_config.c as well.
> 
> Ken is working on these ... essentially a printf-style argument can deal
> with both of them.

I was thinking of the srm_command_loop(): it splits the arguments at
whitespace, so it's difficult to parse the DateFormat="format with spaces"
into a single ITERATE2 argument. But I just checked: IndexOptions takes
RAW_ARGS anyway, so it would have to deal with it internally.

    Martin
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: mod_autoindex (was: Year 2000 Compliance)

Posted by Dean Gaudet <dg...@arctic.org>.
On Thu, 18 Sep 1997, Martin Kraemer wrote:

> Not quite so. Internally, of course it is compliant. On protocol level,
> too. On the user level, however, not 100% (yet). Think of the mod_autoindex
> directory listings: They display the modification dates as...
> 
>     apache_1.3a1.tar.gz    23-Jul-97 02:23   792k  WinNT-Apache-1.3Alpha
>     apache_1.3b1-19970915..15-Sep-97 09:01   864k
> 				  ^^
> That's a 2-digit-year allright. But I was thinking of fumbling with
> mod_autoindex anyway, why not fix that as well. ;-)
> 
> What mod_autoindex needs IMO is
> 
> *   The width of the File Column and Description Column ought to be
>     user-definable, I was thinking of new
> 	IndexOptions   FileColumnWidth=nnn DescColumnWidth=nnn
> 
> *   The date should be Y2kC (Year2000Compliant) -or at least
>     programmable (strftime comes to mind).  But a new parser for, e.g.,
> 	IndexOptions   DateFormat="%d. %B %Y"  DateColumnWidth=17
>     would influence other core sources like http_config.c as well.

Ken is working on these ... essentially a printf-style argument can deal
with both of them.

> *   general cleanup: prohibit invalid options like
> 	IndexOptions IconHeightIsAValidKeywordButThisShouldntBe

Eww. 

Dean