From Newsgroup: alt.os.linux.mint

On 7/18/2026 1:20 AM, Wendelin Uez wrote:

On my android smartphone I have assigned following Tasmota
....
This works very fine, except that the device's answer page
is buffered in Firefox....
....
I know this trick, but I don't know how to implement in a one-liner.

Getting this timer value needs a javascript function, but....

Are you sure that it's Firefox that's caching
the page? Web server caches pages as well.

You need to force the web server (e.g. Apache,
router firmware) to "forget" its cached pages
if you cannot do it from client side
(e.g. Firefox).

Did you really use the trick I suggested? Did
it work or not? Did you just wanna fool around
to troll honest programmers? :)

Are you also trying to create A.I. that
fools around? Well....

Here is my trick again:

Try appending a time-stamp to the URL, led by a question
mark. It's a typical web programming trick.

http://192.168.178.91/cm?cmnd=Power%20off?2026071612121211

Notice the part "?yyyymmddhhmmss": yyyymmdd is date,
followed by "hhmmss" which is time.

AND... AND....

If you could not do anything against the
firmware/web-server and Firefox was not
to be blamed, the only last solution is
to file a complaint against the firmware
comapny? :)



Related:

About - Tasmota
<https://tasmota.github.io/docs/About/>

what is Tasmota - Google uELo#i <https://www.google.com/search?q=what+is+Tasmota>
--

@~@ 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 Newsgroup: alt.os.linux.mint

Mr. Man-wai Chang, 2026-07-18 05:26:

On 7/18/2026 1:20 AM, Wendelin Uez wrote:

On my android smartphone I have assigned following Tasmota
....
This works very fine, except that the device's answer page
is buffered in Firefox....
....
I know this trick, but I don't know how to implement in a one-liner.

Getting this timer value needs a javascript function, but....

Are you sure that it's Firefox that's caching
the page? Web server caches pages as well.

You need to force the web server (e.g. Apache,
router firmware) to "forget" its cached pages
if you cannot do it from client side
(e.g. Firefox).

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.

Try appending a time-stamp to the URL, led by a question
mark. It's a typical web programming trick.

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

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.
--
Arno Welzel
https://arnowelzel.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

Arno Welzel, 2026-07-21 16:21:

Mr. Man-wai Chang, 2026-07-18 05:26:

On 7/18/2026 1:20 AM, Wendelin Uez wrote:

On my android smartphone I have assigned following Tasmota
....
This works very fine, except that the device's answer page
is buffered in Firefox....
....
I know this trick, but I don't know how to implement in a one-liner.

Getting this timer value needs a javascript function, but....

Are you sure that it's Firefox that's caching
the page? Web server caches pages as well.

You need to force the web server (e.g. Apache,
router firmware) to "forget" its cached pages
if you cannot do it from client side
(e.g. Firefox).

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.

Try appending a time-stamp to the URL, led by a question
mark. It's a typical web programming trick.

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.

--
Arno Welzel
https://arnowelzel.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.mint

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 Newsgroup: alt.os.linux.mint

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