Warning about upgrading to apache 1.3.4
- To: email@example.com, Georg Hitsch <firstname.lastname@example.org>, Andrew Howell <email@example.com>, Peter Shtinkov <firstname.lastname@example.org>, Michael Kyed <email@example.com>, Vincent Renardias <firstname.lastname@example.org>, Sven Rudolph <email@example.com>, firstname.lastname@example.org, Ho-sun Lee <email@example.com>, Miquel van Smoorenburg <firstname.lastname@example.org>, UCT LUG <email@example.com>, Enrique Zanardi <firstname.lastname@example.org>, Phil Hands <email@example.com>, Mike Shields <firstname.lastname@example.org>, Andreas Mueller <email@example.com>
- Subject: Warning about upgrading to apache 1.3.4
- From: "James A. Treacy" <firstname.lastname@example.org>
- Date: Sat, 30 Jan 1999 03:03:21 -0500
- Message-id: <[🔎] 19990130030321.W26597@debian.org>
There is a bug in lynx that has been around for over a year that
only surfaces with apache 1.3.4. Lynx is sending a header that
is being used for another purpose under http/1.1. Lynx
does not support the actual feature.
The end result is that under lynx with apache 1.3.4 no content
negotiation is done. Apache sends lynx a list of variants for
the available page and the user needs to select the actual
Only upgrade to apache 1.3.4 if you can live with this.
The next versions of both apache and lynx will have patches to
work around the problem.