Vivaldi caches 500 error response and refuses to connect
-
I have a web service running in Azure, and was doing an update. During the update I tried connecting with Vivaldi, and got a 500 error. After the update, even although other browsers work fine, and Vivaldi itself in private mode works fine, I cannot open the site - Vivaldi is just replying with the same 500 error. Somehow it is remembering the error response.
I've tried CTRL-F5, CTRL-SHIFT-R and so on - no difference.
Developer mode confirms that Vivaldi is serving from the in-memory cache - but this persists even through a system reboot.
What is Vivaldi doing? How do I get Vivaldi to forget the previous error?
-
@gavinbrebner Hi, this shouldn't happen, it should not use cache for http error codes.
Do you have a url to test with?
Have you tried clearing all cache in any case?This link will always generate a 500:
https://httpstat.us/500
http://returnco.de:500Vivaldi does not use cache here for me, even with "Disable Cache" set in Devtools:
(Win10 x64, but I doubt this would be OS-related)
-
@gavinbrebner Same in Private Window?
-
Vivaldi should not be caching 500 responses, have you made sure it's not something related to your session?
Try clearing the cookies for the site and try refreshing.
