Score:0

Nginx chunked transfer encoding behavior

jo flag

I am trying to understand how the chunked transfer encoding is supposed to work for a client that is requesting content from nginx in the following Scenario:

ffmpeg is producing video segments (.ts, m3u8) for an incoming live video stream. I want to use chunked transfer encoding for the client that is requesting this content from Nginx in the two cases

  1. Web-server mode (content is locally sourced with 'root' directive under the location block. Nginx is producing the content to a designated folder that is being served out by nginx

  2. Reverse Proxy mode (upstream origin). Nginx is accessing the web-server (could be local or another machine) to get the content.

Would chunked transfer for both the above cases from a client's perspective? Can someone share the corresponding nginx config snippet for this??

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.