My current suggestion would be that actix-web should just drop empty chunks from the given stream (this is what I did to solve the issue), but there might be another view on that. It aligns with HTTP standard in a way: chunked response is terminated by a chunk with 0 length, but makes the usage of the framework a bit confusing (it took me a day to figure out the reason of this wired behavior). What happens is that if I request the endpoint requiring compression I'm getting the full response, but if I request it uncompressed I get only the part of data (the one before the first empty chunk). I stream some response by chunk and some chunks are empty. I've ran into the following issue recently while returning chunked encoded response:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |