[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Incorrect content-type-headers
|
From: |
Michael Warner |
|
Subject: |
Re: lynx-dev Incorrect content-type-headers |
|
Date: |
Thu, 18 Jun 1998 23:08:54 -0700 |
On Thu, Jun 18, 1998, Philip Webb <address@hidden> wrote:
> 980618 Ari Moisio wrote:
> > There were some discussions about incorrect content-type-headers & Lynx.
> > Problem is misconfigured site which sends text/plain -header
> > instead of text/html and Lynx does not render the page.
> > I haven't found any way to force Lynx to handle page as text/html ,
> > -force_html seems not to help. Problematic url is
> > http://www.nkl.fi
> > national federation for visually handicapped in Finland.
>
> i found the same thing with 2-8pre.2, but <head> does say text/html :
Wrong head, I think - a HEAD request (']') shows text/plain.
[...]
> the problem seems to be incorrect syntax following content= :
> after i amended it to:
[...]
> the problem appears to be solved
I think you probably saved the file with a .htm(l) extension, in
which case it didn't (for me) matter what was in the <META ...>
tag, it showed up rendered. When I renamed the file without the
extension, it showed up as source, again irrespective of the META
content.
That's without -force_html, of course, which *will* make a
difference rendering a local file, right?
--
Michael Warner
<address@hidden>
Re: lynx-dev Incorrect content-type-headers, David Woolley, 1998/06/20