[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev linebreaks in attributes
From: |
Thomas E. Dickey |
Subject: |
Re: lynx-dev linebreaks in attributes |
Date: |
Thu, 29 Nov 2001 20:22:00 -0500 (EST) |
On Fri, 30 Nov 2001, Dick Wesseling wrote:
>
> Lynx Version 2.8.4rel.1 has problems with
>
> http://thertcgroupinc.goemerchant2.com/nscgi-bin/thertcgroupinc/index.cgi?Merchant=thertcgroupinc
>
> This page contains the following idiom:
>
> <A href="broken?par1=x
> &par2=y">testme </a>
>
> Lynx translates the linebreak into an unencoded space which results in
> a malformed HTTP request.
>
> According to the HTML4 specs one is supposed to replace carriage
> returns with (encoded?) spaces and ignore linefeeds within cdata. So
> technically speaking lynx is correct in this case.
> However, Lynx also replaces a linefeed by itself with a space, which is
> NOT correct.
>
> So much for theory. In practice the other guys ignore both carriage-and
> linefeed, so the code above is handled as
>
> <A href="broken?par1=x&par=y">testme </a>
This change in 2.8.5dev.4 addresses that (but I agree it's still not a
good fix):
* modify LYLegitimizeHREF() change from 2.8.4dev.21 to eliminate newlines from
the HREF rather than converting them to spaces. This fixes a problem with
www.ebay.com which splits up HREFs with newlines. Changing the newlines to
spaces made the HREF no longer match, e.g., when it was built up from
a CGI script (report by Morten Bo Johansen) -TD
--
T.E.Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden