[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV lynx, text/html and non-standard suffixes
From: |
Foteos Macrides |
Subject: |
Re: LYNX-DEV lynx, text/html and non-standard suffixes |
Date: |
Tue, 01 Jul 1997 13:58:58 -0500 (EST) |
Al Gilman <address@hidden> wrote:
>The most common source of this problem is mis-configuration of
>servers.
>
>Lynx follows the type indicated by the server in the HTTP header
>fields when the file in question is passed to Lynx as an HTTP
>message. If the server correctly identifies the message as
>text/html Lynx will process it accordingly.
>
>There are workarounds you can apply on the Lynx side but the
>origin of the problem is mis-management of the site serving you
>the page.
My reading of the original message also was that it is a
problem of a mismanaged server, and that suffix maps have nothing
to do with it on Lynx's end. Lynx uses its suffix maps only for
file and ftp URLs, for which a Content-Type header is unavailable.
If the suffix is not mapped to a default in HTInit.c, you can map
it (e.g., for .ht1, ht2, etc.) via SUFFIX: lines in lynx.cfg or
entries in the global or a personal mime.types file.
Fote
=========================================================================
Foteos Macrides Worcester Foundation for Biomedical Research
address@hidden 222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
- Re: LYNX-DEV lynx, text/html and non-standard suffixes, Al Gilman, 1997/07/01
- Re: LYNX-DEV lynx, text/html and non-standard suffixes,
Foteos Macrides <=
- Re: LYNX-DEV lynx, text/html and non-standard suffixes, David Woolley, 1997/07/02
- Re: LYNX-DEV lynx, text/html and non-standard suffixes, Foteos Macrides, 1997/07/02
- Re: LYNX-DEV lynx, text/html and non-standard suffixes, Foteos Macrides, 1997/07/04