www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Klaus Weide <kwe...@enteract.com>
Subject protocol/5455: Lynx misinterprets Content-Location
Date Sat, 11 Dec 1999 00:15:51 GMT

>Number:         5455
>Category:       protocol
>Synopsis:       Lynx misinterprets Content-Location
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Fri Dec 10 16:20:03 PST 1999
>Originator:     kweide@enteract.com
To quote someone else:
Client Bug!  Not an apache bug!  I couldn't find the appropriate
category for client bugs.

All known Lynx versions (well, at least since 2-5, 1996) have a bug
that causes a "Content-Location:" header field to be mis-recognized
as "Location:" in redirection responses, if the "Content-Location:"
precedes the "Location:".  (This applies only to messages with
redirection status codes 301,302,etc., where the Lynx code takes some
shortcuts instead of doing full header parsing.)

This was never discovered until recently - apparently such a
combination of header fields hasn't been common.  Recently the
problem was reported to the lynx-dev list.  Please see
for the original report, including headers.  (It appears that
conneg creates redirection messages with "Content-Location:"?)

This is being corrected in the current Lynx development code.
Apache isn't doing anything wrong here.  But could Apache work around
the problem, for those Lynx copies out there?
with any moderately recent version of Lynx.  You'll end up at the
wrong page after the redirection(s).
(a) Always send any "Location:" header fields before any "Content-Location:",
    in all responses (all 30x responses would be enough, x > 0).  Or
(b) something like (a), or perhaps suppressing "Content-Location:", under
    control of BrowserMatch.
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message