[FFmpeg-devel] [PATCH] mmsh:// "400 bad request" fix

[Kirill Zorin]

Yeah, some kind of Gmail oddity. I'll see how to fix it for next time.
Is it okay to attach the .patch file to the email, or will the mailing
list robot reject it?

On 16 June 2011 14:58, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Thu, Jun 16, 2011 at 11:29:28AM -0400, Kirill Zorin wrote:
>> There is no need to write two HTTP newlines (\r\n) into "headers",
>> because http_connect (in http.c) already appends one HTTP newline at
>> the end of the given headers chunk, which would result in sending
>> three HTTP newlines after the headers. Most of the time it's okay
>> (although not RFC-conforming), but many proxy servers and the
>> occasional strict httpd will puke with a "400 bad request".
>>
>> ---
>>  ffmpeg/libavformat/mmsh.c |    4 ++--
>>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> applied, thx
>
> btw your patches are a bit oddly formated
>
> [...]
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> The worst form of inequality is to try to make unequal things equal.
> -- Aristotle
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAk36UjgACgkQYR7HhwQLD6uSsgCdG+2Fipsf6TYdVOvTIMLMoSa/
> +gYAnjXpcAXLf1DLqSSlBFMT7oVsR9n3
> =7n2v
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
>