latest development build 2.0.9.4rc2 should work-around this router web server implementation bug automatically, without any preference change.
Please check it, after reverting the noscript.doNotTrack.* preferences to their default values.
Users browsing this forum: Bing [Bot] and 4 guests