GNOME Bugzilla – Bug 645676
Vimeo needs quotations in header params even if they are tokens
Last modified: 2011-03-30 22:58:33 UTC
Created attachment 184235 [details] [review] Half baked fix When uploading videos to Vimeo's endpoint with a POST multipart/form-data, it will return a 500 error if Content-Disposition param values are not quoted. *sigh* I mentioned it in their forums: http://vimeo.com/forums/topic:35969
yeah, someone else hit this too. the half-baked fix won't work because there are servers with the opposite bug (will only accept tokens) on other headers. the 3/4-baked fix would be to make soup-multipart.c just call soup_header_g_string_append_param_quoted(), except that would break UTF-8-encoded filename parameters. I think the fully-baked fix is to rearrange the code in soup_header_g_string_append_param() and soup_header_g_string_append_param_quoted() so that _quoted() can handle both quoted-strings and UTF-8, and then make soup-multipart use that. *** This bug has been marked as a duplicate of bug 641280 ***
Created attachment 184748 [details] [review] Use quoted values in Content-Disposition headers. This fixes a Vimeo bug where its upload endpoint only accepts Content-Disposition values that are quoted. Even though RFC 2231 explicity says that servers should accept mix of quoted and unquoted values. http://vimeo.com/forums/topic:35969