lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Lynx 2.8.1rel.2 - HTTP bug?


From: Leonid Pauzner
Subject: Re: lynx-dev Lynx 2.8.1rel.2 - HTTP bug?
Date: Fri, 16 Apr 1999 11:56:06 +0400 (MSD)

11-Apr-99 17:10 Dirk Foersterling wrote:
> Hi,

> I found lynx (2.7.x, 2.8.0 and 2.8.1) sending incomplete HTTP requests.
> For example retreiving the URL http://lynx.browser.org/ with lynx
> (_not_using_any_proxy_) results in an error message (Bad Request). I
> tracked it down and found lynx forming a request beginning with

> GET  HTTP/1.0
> Host: lynx.browser.org

> which seems to be incorrect, because of the empty URI/path after GET.
> A proxy usually inserts the missing "/" here, so the problem only shows
> up in direct lynx/httpd communication. I tried this on several http
> server software including Apache-1.3.6 and MS-IIS 4, to verify that not
> a specific server version is picky about empty URIs.

I was trying http://lynx.browser.org with and without proxy -
"/" path sent, but apparently without hostname in this field.
Is it correct?


Composing Proxy Authorization for proxy.mccme.ru:3128/http://lynx.browser.org/
HTAASetup_lookup: No template matched `http://lynx.browser.org/' (so probably 
not protected)
HTTP: Not sending proxy authorization (yet).
Writing:
GET http://lynx.browser.org/ HTTP/1.0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Host: lynx.browser.org
Accept: text/html, text/plain, text/sgml, */*;q=0.01
........
and

Composing Authorization for lynx.browser.org:80/
HTAASetup_lookup: No template matched `' (so probably not protected)
HTTP: Not sending authorization (yet).
Writing:
GET / HTTP/1.0
^^^^^
Host: lynx.browser.org
Accept: text/html, text/plain, text/sgml, */*;q=0.01
Accept-Encoding: gzip, compress
Accept-Language: en,ru
Accept-Charset: windows-1251;1.0,*;0.5, iso-8859-1;q=0.01, us-ascii;q=0.01
User-Agent: Lynx/2.8.2dev.22 libwww-FM/2.14
Referer: http://www.slcc.edu/lynx/current/


BTW, developers, no_cache lync.cfg variable can not be reloaded via
reload_read_cfg() at run time currently - only for next session.
Will fix this also.

>  -dirk

> --
>                    D i r k   F "o r s t e r l i n g
> address@hidden  ********  http://www.DeathsDoor.com/milliByte/
>                            -------------
>             ISDN - [I]st [S]owas [D]enn [N]oetig?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]