1. Forum
  2. USENET
  3. comp.mobile.android

  • Re: how to avoid buffering?

    From Mr. Man-wai Chang@toylet.toylet@gmail.com to alt.comp.software.firefox,comp.infosystems.www.authoring.html,comp.lang.c,comp.mobile.android,alt.os.linux.mint on Wed Jul 22 22:03:51 2026
    From Newsgroup: comp.mobile.android

    On 7/21/2026 10:21 PM, Arno Welzel wrote:

    Tasmota does not cache anything at all - this runs on a tiny
    microcontroller without much RAM. They can not afford to spend that
    memory for caching.


    You don't infer from hardware spec. You have to test
    things using tools like ncat to find out.

    Maybe Wendelin Uez <wuez@online.de> should restart
    Tasmota whenever he/she thought its caches was
    not cleared? It possibly is the last resort. :)

    I presume Android don't do strange things when
    it comes to caching. And we don't know what
    hardware and ISP Wendelin Uez is using.

    Anyway, the caching is either in the server or
    the client. Firefox could be trusted as far as
    most know.

    Yes, but an ugly one as all old versions also stay
    in the cache and fill it up. Better would be to
    send an appropriate headers in the HTTP response:

    Cache-Control: no-store, no-cache, must-revalidate, max-age=0
    Expires: 0

    Complete list:

    Cache-Control: no-store, no-cache, must-revalidate, max-age=0
    Expires: 0
    Pragma: no-cache

    However, I don't think, that there is a configuration
    option for that, you may have to patch the web
    server code of Tasmota to do this.
    --

    @~@ Simplicity is Beauty! Remain silent! Drink, Blink, Stretch!
    / v \ May the Force and farces be with you! Live long and prosper!!
    /( _ )\ https://sites.google.com/site/changmw/
    ^ ^ https://github.com/changmw/changmw
    The game is afoot... Meow...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Arno Welzel@usenet@arnowelzel.de to alt.comp.software.firefox,comp.infosystems.www.authoring.html,comp.lang.c,comp.mobile.android,alt.os.linux.mint on Fri Jul 24 09:05:21 2026
    From Newsgroup: comp.mobile.android

    Mr. Man-wai Chang, 2026-07-22 16:03:

    On 7/21/2026 10:21 PM, Arno Welzel wrote:

    Tasmota does not cache anything at all - this runs on a tiny
    microcontroller without much RAM. They can not afford to spend that
    memory for caching.


    You don't infer from hardware spec. You have to test
    things using tools like ncat to find out.

    How does ncat show you, if the *server* cached a page, before it was
    sent to the client?

    Also look at the code of Tasmota - there is no server side chaching.

    Maybe Wendelin Uez <wuez@online.de> should restart
    Tasmota whenever he/she thought its caches was
    not cleared? It possibly is the last resort. :)

    No, this does not help, when the *browser* caches the result. That's the reason, why Tasmota has an API to access data and you usually control
    devices not using Tasmota directly but with an MQTT broker like Home
    Assistant.

    I presume Android don't do strange things when
    it comes to caching. And we don't know what
    hardware and ISP Wendelin Uez is using.

    No, the same things happen in desktop browsers as well. When a webserver
    does not send any headers which forbid caching, a website is *always*
    cached.
    --
    Arno Welzel
    https://arnowelzel.de
    --- Synchronet 3.22a-Linux NewsLink 1.2