If it's indeed caching it won't have affected a lot of noobs at all since for it to come up you'd need to have had an older/different version of OctoPrint running on the same address in the past for your browser to get a chance to cache it. And I think the default cache duration isn't that long either so you'd need to have that done within the past day or so.
In any case, that was an issue and it might have caused other kinds of problems in the field, so this definitely is better this way.