Beast mode!
Thank you!
Some good stuff in there. If I have time, I’ll check it out tonight. I’m mostly curious about extension caching when an extension is updated.
I don’t know if it’s live yet, but I saw an option was added to the web installer for uploading WebUI v3.
It has, but it won’t trigger in the installer until a new FluidNC build gets published
if you are referring to
“Stop from disabling cache when extensions are loaded”
The WebUI, when it was loading extensions, would force a timestamp into the request to make sure that it would bypass cache checks.
With the cache changes I made in FluidNC 3.9.1+, and this new WebUI, it should properly use File Hashes and ETags to work out whether it should be sent back, and no longer add timestamps to the requests.
So as long as the hash of the file changes, it should work.
I also made the hash check happen before the $HTTP/BlockDuringMotion check as well, so it should reduce flash load issues and web request denials from appearing if you happen to load the WebUI during a job
@Michael_Melancon
Thanks a bunch! Sorry for the “potential mega thread” aspect of asking here.
I just updated to the latest WebUI v3 and to FluidNC built from the main branch. I didn’t poke it too much but it seems fine.
I think it’s always done this, but it seems to like to double-load extensions. This is after reloading the extension after an update to it. I don’t think there’s an issue here, just an observation.
All 4 of those are for the same file but it did seem to only download it once. I see that it did the 200 and then went back to the 304. I don’t quite understand what the blobs are for but I assume it has to do with how extensions are implemented.
Yeah.
I think the double request thing came in when Luc added the extension caching or something.
The mechanism it uses, if I remember correctly, is to download it to local storage, then load it from there.
The blob load I think is when it’s pulling it out of local storage.
It’s at least using the cache correctly and not double loading.
Previously you would have seen 2 full downloads from the ESP32 there.
The double load is the next thing I will look at.
I spent a little bit of time before I left last time looking, but ran out of time.
I may just send it to Luc, and see if he’ll look into it first 
@jeyeager Fixed.
That Release didn’t include the index.html.gz file like the other releases.
Sorry, should be there now.
I had to delete the release and recreate it earlier, so I must have forgot to attach it when I recreated it
It seems like the tag is wrong. It seems to point at a version without the FluidNC changes.
Try again, I had to recreate the tag
