Snapshot 1.0.340.7 yields apache server error on particular site
When visiting www.kwvfrisia.nl or http://www.fieldstar.nl with the latest snapshot i get an error 409: Conflict The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache Server at www.kwvfrisia.nl Port 80 This appears to be a server issue as these sites are hosted at the same provider, however it is not the case in an older vivaldi version, nor in firefox or other browsers. So, what's going on?
Can confirm this problem.
I think, the server has a filter for browsers which is working incorrect.
I reported that as bug VB-11282 as high prio to Vivaldi devs.
Which older Vivaldi loaded the pages?
Found the problem, the browser sends incorrect HTTP header User-Agent
Workaround (not a good fix i know):
1. Install extension https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg
2. Select button Chrome UA SPoofer
3. Select Firefox
4. Open you webpage which does not display
All shows fine
Dont forget to switch back to Chrome -> Default on other sites.
Ah, if you open Vivaldi Extensions manager and go to "User-Agent Switcher for Chrome" there is a Options link.
There you can change settings of the extension.
And in setting Permanent Spoof list you can set permanently a User Agent for your disfucntional domains.
Thats better than switching with extension button back and reverse.
I hope that will help you until the next Vivaldi Snapshot has a fixed bug and you can remove the extensioin.
Thank you for sorting this out.
Can you tell me what exactly is wrong with the http user agent the browser is sending?
As far as i can see it sends: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36 Vivaldi/1.0.
The bug is still present in version 1.0.344.5 (Beta) dev (64-bits)
Internally the bug is fixed now.
In next relased Snapshot it will be fixed, i think.
Fixed in 1.0.344.24