[Bug] Visiting page redirects to data:image/svg+xml

[Lee245]

Describe the bug

When visiting the page mentioned below, it first loads the page, but then automatically redirects to "data:image/svg+xml,%3Csvg xlmns='http://www.w3.org/2000/svg' width='980' height='551'/%3E". On the default Android browser and on Fennec, the page loads just fine.

To Reproduce

Steps to reproduce the behavior:

1. Go to https://tweakers.net/reviews/8806/harvest-moon-one-world-beter-maar-nog-steeds-tegenvallend.html
2. See error

Expected behavior

Page shown properly.

Screenshots

Device Info

• Device: Samsung Galaxy S5
• OS: LineageOS 16.1 (Android 9.1)
• App version: 12.1.1

Additional context

[CookieJarApps]

Would it be possible for you to check if this occurs in other WebView browsers (e.g. Lightning, Via, Soul or FOSS Browser) on your device? Thanks for reporting the bug.

[Lee245]

Thanks for looking into this! I checked with both the standard LOS browser (which I assume also uses WebView) and the FOSS browser. No issues there. Could it be related to any browser settings?

[CookieJarApps]

If you exported your settings in the browser and pasted the contents of the exported txt file here, I can try importing your settings and seeing if any of those cause this issue.

[Lee245]

Thanks. I also have the same issue when using Midori, which is very similar to this browser. Here's the settings export;

"stopIntent"="false","preferHTTPS"="true","ssl"="true","thirdParty"="true","search"="12","imageUrl"="","alwaysincognito"="false","cache"="true","AdBlock"="true","colorMode"="false","lastTab"="false","blackStatusBar"="false","doNotTrack"="true","firstLaunch"="false","fullscreen"="true","clearCookiesExit"="true","Theme"="1","agentchoose"="3","force"="true","secondBar"="false","searchSuggestionsChoice"="1"}

[Genau6502]

Thanks. I also have the same issue when using Midori, which is very similar to this browser. Here's the settings export;

"stopIntent"="false","preferHTTPS"="true","ssl"="true","thirdParty"="true","search"="12","imageUrl"="","alwaysincognito"="false","cache"="true","AdBlock"="true","colorMode"="false","lastTab"="false","blackStatusBar"="false","doNotTrack"="true","firstLaunch"="false","fullscreen"="true","clearCookiesExit"="true","Theme"="1","agentchoose"="3","force"="true","secondBar"="false","searchSuggestionsChoice"="1"}

Yes, that's because midori is literally a copy/paste job of smart cookie...

[0xRustlang]

I also had this issue with some websites i opened from google search but i don't remember the websites and the search url to share unfortunately.

[CookieJarApps]

Thanks. I also have the same issue when using Midori, which is very similar to this browser. Here's the settings export;

"stopIntent"="false","preferHTTPS"="true","ssl"="true","thirdParty"="true","search"="12","imageUrl"="","alwaysincognito"="false","cache"="true","AdBlock"="true","colorMode"="false","lastTab"="false","blackStatusBar"="false","doNotTrack"="true","firstLaunch"="false","fullscreen"="true","clearCookiesExit"="true","Theme"="1","agentchoose"="3","force"="true","secondBar"="false","searchSuggestionsChoice"="1"}

Thanks, I'll import those settings and see if I can recreate the issue.

[Lee245]

Any updates on this issue? I run into this problem quite regularly for different websites.

[CookieJarApps]

It's definitely to do with the Do Not Track setting - disabling it fixes the issue. I suspect that this is a WebView bug, but I'll look into setting the headers differently in the browser to try and fix this and some of the crashes relating to the Do Not Track, Request 'Save-Data' and Remove Identifying HTTP Headers options.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Kita2345]

Unstale

[Kita2345]

Reopen

[Lee245]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This bug is still relevant.

[Lee245]

It's definitely to do with the Do Not Track setting - disabling it fixes the issue. I suspect that this is a WebView bug, but I'll look into setting the headers differently in the browser to try and fix this and some of the crashes relating to the Do Not Track, Request 'Save-Data' and Remove Identifying HTTP Headers options.

Any updates on this bug? @CookieJarApps