bug#35658: 27.0.50; Problems with chunked/gzipped content in url-http

[Lars Ingebrigtsen <larsi@gnus.org>]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> So some thing is doing ... something to the data as it arrives from
> Facebook.  url-http is working in a multibyte buffer, so I guess there
> are many possible reasons for this happening...

Nothing so complicated -- if I remove the contents of
url-http-chunked-encoding-after-change-function, the text is all there,
so it's doing something very wonky.

What seems to happen is that Facebook will output the first character of
the chunked header first, and then the rest afterwards.  This somehow
makes that function delete parts of the header before it's gotten the
complete header, which again means that it'll never find the real size
of the data.

And it's a function that's virtually impossible to debug in any sensible
manner, because everything happens async and the function depends on
many buffer-local variables...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no