Page 1 of 1
User-Agent issues
Posted: Thu Sep 15, 2022 9:27 pm
by gjf
With the current Windows version (103.0.5250.0 64 bit) some issues with default user-agent leads to blocking on some sites, medium.com for instance.
The block is performed by Cloudflare firewall. Changing user-agent to "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36 Edg/105.0.1343.33" (Edge default value) solves the problem.
Maybe devs should pay attention on it in future updates.
Re: User-Agent issues
Posted: Tue Feb 07, 2023 11:36 am
by Hotcakes
Just wanted to say thanks.
I am still running on v88 and this seems to have helped a lot :p
Re: User-Agent issues
Posted: Thu Apr 03, 2025 10:29 am
by Hotcakes
I have begun experiencing new issues with the Cloudflare firewall. It seems they don't like the Edge portion of the agent string when using Iron anymore. This is a new issue that's popped up some time after October 2024.
A modified version of the default Iron string works fine:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36
where the Iron tag is removed, because it breaks compatibility with other websites (Yahoo Mail tested).
Re: User-Agent issues
Posted: Wed Apr 09, 2025 5:38 am
by AdalineMHannon
Most importantly, either modify your User-Agent to a more recognized User-Agent, like the default Edge string, to effectively bypass these restrictions, or consider updating regularly.
Re: User-Agent issues
Posted: Fri Apr 11, 2025 8:49 am
by LeslieBourg
AdalineMHannon wrote: ↑Wed Apr 09, 2025 5:38 am
Most importantly, either modify your User-Agent to a more recognized User-Agent, like the default Edge string, to effectively
Geometry Dash Lite bypass these restrictions, or consider updating regularly.
Can you elaborate on how to use user agents? This is important and I would like to know more.
Re: User-Agent issues
Posted: Sun May 04, 2025 5:28 am
by pstein
Just want to confirm this problem for WhatsApp webapp:
https://web.whatsapp.com/
I suggest to fake (at least optionally) the UserAgent string if such wide spread webservices like WhatsApp WebApp insist on not serving certain UserAgents
Re: User-Agent issues
Posted: Sun May 04, 2025 1:20 pm
by Hotcakes
As I pointed out, the default User Agent string works fine with the Iron portion stripped out. No need to fake anything, other than ignoring Irons existence, which I guess I why SRWare leave it in. Can confirm WhatsApp Web is working fine with the string I posted above.
Re: User-Agent issues
Posted: Mon May 05, 2025 5:57 am
by pstein
Hotcakes wrote: ↑Sun May 04, 2025 1:20 pm
As I pointed out, the default User Agent string works fine with the Iron portion stripped out. No need to fake anything, other than ignoring Irons existence, which I guess I why SRWare leave it in. Can confirm WhatsApp Web is working fine with the string I posted above.
How do I "strip out the iron portion?"