Le 2015-10-13 20:47, Luca Barbato a écrit :
On 13/10/15 18:21, Rémi Denis-Courmont wrote:
Le 2015-10-13 12:44, Martin Storsjö a écrit :
From: Carl Eugen Hoyos <[email protected]>
Some overly strict implementations require this, even though it
technically is incorrect according to the spec.
That's not overly strict, that's just plain broken. Overly (or not
so
overly) strict implementations require that there be no quotes here.
It might be a good idea to accept invalid extraneous quotes for IOP.
Sending invalid messages ones on purpose is insane. The problem is
known
and the conclusion from RFC7616 was to verry explicitly FORBID
quotes.
You suggest to drop the patch or to update the commit message (I
already
amended it with s/overly strict/faulty/ locally.)
I suggest dropping the patch.
Postel's principle is to be strict in what you send, relaxed in what
you accept. Though there has been recent push for being strict both ways
due to, notably, security concerns.
There never was a reasonable proposal to be relaxed in what you send,
for a good reason.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
