In case that is no joke "confirm form resubmission" exchange popup, it regularly happens on Chrome on invigorate or subsequent to squeezing a back catch. In spite of the fact that it's been seen on different programs like Firefox: confirm form resubmission on firefox
It will likewise once in a while give the error code "ERR_CACHE_MISS". It's less an error, in any case, all the more an 'include', as indicated by Super User blurbs who have researched the issue.
Whatever the case, numerous web clients are attempting to make sense of how to turn it off. Initially, we should investigate why it occurs.
For what reason Does It Happen
As indicated by a Super User publication, Chrome presented this "highlight" to keep programs from inadvertently copying POST activities on forms.
For instance, purchasing a similar thing twice. On the off chance that you invigorate a page subsequent to purchasing something, your Mastercard could be charged twice in the event that you weren't approached to "confirm form resubmission".
Getting increasingly specialized, the client says that there was a fix on before Chrome summons that utilized the - impair brief on-repost parameter, yet this likewise was broken in later forms.
Further, regardless of many Chrome client grumblings and bug reports this issue has stayed diligent.
Muddling it, this Super User blurb says, is that the Chrome module that backs/forward is constructed so ineffectively that it is almost difficult to fix.
Furthermore, no Google designer is daring enough to revise it without any preparation.
Step by step instructions to Fix It
Method #1 (Super User Theories)
The Super User says that on the off chance that you can't really alter the page containing the POST activity, at that point there truly isn't any arrangement.
Then again, he says, in the event that you can alter the page there are two potential arrangements:
Utilize GET rather than POST
Utilize the Post/Redirect/Get technique with the HTTP 303 reaction code
In case you're only a customary program, that is clearly very little help. How about we proceed onward to the following fix.
Method #2 (Google Forum Fix)
One Chrome client over in the Google Product Forum client said this 'include' has formed into genuine inconvenience.
He's experiencing the message all the time and might want to cripple this capacity. It expects him to reload a site page at whatever point he explored back to a powerfully made page.
He censured it as incredibly disturbing because of the reality a wide range of pages will trigger the message.
A client posted the accompanying fix. Use it at your very own tact:
Right-click on your Chrome alternate way symbol and select Properties
In the objective field, include in: "- cripple brief on-repost" (no statements after chrome.exe)
He gave a model his objective field resembled:
C:\Users\John\AppData\Local\Google\Chrome\Application\chrome.exe - cripple brief on-repost
Close down and re-open Chrome utilizing the alternate way and check whether you experience the issue once more.
Method #3 (Don't Use The Back Button)
Another workaround originates from a Chrome client who clarified this isn't a bug however happens in light of the fact that Chrome doesn't reserve POST.
The workaround, so as to "debilitate" it, Chrome programs should quit utilizing the back catch after you have presented a form.