I have noticed on several occasions as I am testing, that once I try to access a file from within an app and that file is NOT found, the error is cached within the browser. Even after correcting the issue, the cached error persists UNTIL a “clear browsing data” action is performed. At times, I have to clear the browsing data more than once for the error to be corrected.
This behavior is not the best for user experience.
Is there a way to force a “refresh” of the file path result so the correct information shows once a file or error has been updated/corrected? Or alternatively, is there a way to PREVENT caching when an error has occurred such as “FILE NOT FOUND”?