Image streaming over mongoose web server

[Jakob T]

Is it possible for the streaming feature to work over the mongoose server? I had thought streaming was working by default based on my logs. However once we started deploying images over cellular networks I noticed we have to wait for the swupdate file to be completely uploaded before the stream starts.  

Looking at the documentation I do see: "The temporary copy is done only when updated from network. When the image is stored on an external storage, there is no need of that copy."

Is this a limitation of mongoose itself?

Thanks

Jakob

[Stefano Babic]

Hi Jakob,

On 11/5/25 20:28, Jakob T wrote:
> Is it possible for the streaming feature to work over the mongoose
> server?

Yes, it works out of the box.

> I had thought streaming was working by default based on my logs.
> However once we started deploying images over cellular networks I
> noticed we have to wait for the swupdate file to be completely uploaded
> before the stream starts.

Noted is something different as verified. Depending on system's load and
network speed, the uploaded packets can still be stored in socket
buffers. But SWUpdate does not make any copy if streaming is set via
installed-directly.

>
> Looking at the documentation I do see: "The temporary copy is done only
> when updated from network. When the image is stored on an external
> storage, there is no need of that copy."
>
> Is this a limitation of mongoose itself?

There is not this limitation.

Best regards,
Stefano Babic

>
> Thanks
>
> Jakob
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> swupdate/76b9cd72-a22c-481f-a1f7-1b1978b9c8e2n%40googlegroups.com
> <https://groups.google.com/d/msgid/swupdate/76b9cd72-a22c-481f-
> a1f7-1b1978b9c8e2n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Jakob T]

Hi Stefano,

Thanks for confirming. 

After a wild goose chase it turns out our nginx reverse proxy was buffering the whole file. I needed to add:

proxy_request_buffering off;

to our nginx.conf

Thanks,

Jakob