Thomas Dickey wrote:
Perhaps (by the way, I'd not have used the term "incorrect" if I'd made
the report, since that prejudges the issue).
I don't see a package for disorder, and can only guess which upstream
source it might be.
Reading
http://www.w3.org/Protocols/rfc2109/rfc2109.txt
I see in section 5.1 several examples, with a comment relating the POST
path in them to the prefix. That would be the same path as Lynx is checking
if you ran it with a -trace option and captured the details.
Looking at a Lynx trace file, it seems that the path could begin with /cgi-bin
Firefox does retain the path in its cookie representation; Opera does
not appear to do this; Konquerer has a poor reputation in any case -
so much for examples - let's stick to the RFC as stated.
(a trace file from Lynx running with disorder would show the corresponding
POST or GET, with the path).
I think you must be confused - the HTTP request does not contain the
path. The bug is in Lynx's handling of the response.
ttfn/rjk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
