httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <>
Subject Re: [PATCH] Apache 1.3.4 <-> Lynx 2.[78] compatibility problem
Date Fri, 22 Jan 1999 18:40:14 GMT
>Look, we are talking a TCN *protocol violation* here.  We are not just
>talking the possibility of getting a slightly degraded but still
>acceptable response.  This protocol violation could potentially confuse
>compliant browsers into producing a completely unacceptable response.

Then fix the protocol.  TCN is experimental for a good reason.
If TCN can get confused by a single correct 200 response, then something
is wrong with TCN.  However, I think you are just inventing problems
that do not exist in practice.

>If you make Apache non-compliant to fix a non-compliance bug in Lynx, we
>are worse off than we started.

One has no effect on the other.  TCN recommends a whole bunch of crap
that we are not going to do.  If you insist that we toe-the-line to
every detail of the RFC when doing so has obviously adverse results
for HTTP performance, then I'll just remove it from mod_negotiation
and reduce the problem to the only one that needed to be solved:
giving information in Alternates for agent-driven negotiation.

If you can come up with an actual scenario which is broken by the
implementation, then I'll fix it, but not just because it needs to match
the current RFC.


View raw message