According to Joe R. Jah:
> On Tue, 27 Nov 2001, Gilles Detillieux wrote:
> > Of course it would be possible to make htdig configurable as far as
> > what suffixes it allows for local_urls, but that just reopens the whole
> > issue of how is the best way to do this.  Probably using a mime.types
> > file is the way to go, but someone would have to add this capability
> > to the code.  It's not enough to just give htdig a list of suffxes to
> > allow - you need to tell it what content-type is associated with each
> > suffix.
> 
> How does 3.2x deal with file://?  I guess local_urls is irrelevant there.

Not so much irrelevant as pointless.  It's not entirely irrelevant
because it would be possible to put file:// urls into the local_urls
definition, and then these urls would be read by the local_urls handling
code rather than the file:// handling code.  Ideally, this shouldn't
make a difference, but because we're talking about two separate, and not
necessarily completely bug-free pieces of code, there's the potential for
different results.  E.g. you could conceivably get different content-types
assigned to a specific file name suffix by the two pieces of code.

The file:// handler uses a mime.types file to determine content-type,
while the local_urls handler still uses the same limited, hard-coded
list of content-types as in 3.1.x.  This still needs to be fixed, so
that the local_urls handler ends up using the file:// handler code to
fetch and type files, for the sake of having consistent results.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba  Phone:  (204)789-3766
Winnipeg, MB  R3E 3J7  (Canada)   Fax:    (204)789-3930

_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to