Jump to content

Recommended Posts

Posted

this might have been asked

when you goto history and clear it all is it all really gone from browser or is there a file that retains it all if so where is it

  • 3 months later...

Posted
3 hours ago, DrWho3000 said:

can i safely delete everything in the 360History file in userdata ? and 360History-journal

Yes, if have doubts, just make a backup.

Posted

Could someone using 360Chrome please try this site for me?

www.bbcpa.org.uk

In my copy of 360Chrome 13.5,2036.0 it won't load, it either produces a connection error or just sticks on the new tab page.
I'm pretty sure that it used to work!

It's fine in Thorium and Supermium on XP.
Thanks, Dave.
:)

Posted (edited)
3 hours ago, Dave-H said:

Could someone using 360Chrome please try this site for me?

www.bbcpa.org.uk

In my copy of 360Chrome 13.5,2036.0 it won't load, it either produces a connection error or just sticks on the new tab page.
I'm pretty sure that it used to work!

Hi Dave :P ; I wish I were over at your part of the planet, where you currently have a pleasant 18C, while here we're in the middle of a never-seen-before July heatwave, about to last at least until the 27th (to get an idea, it's 23:34 now and the outside temp is at 35C ! :( ) ...

Back on topic: Your ex-colleagues are simply blocking the version of 360EE you're using (on XP) due to the User-Agent-String it broadcasts; I suppose you're using one of the @NotHereToPlayGames's mods, so inside its loader you'll find the cmdline switch below: 

 --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36"

They outright block :realmad: Chromium 86, so when the browser tries to load that page, it gets served an "errorcode337" and the tab ends up blank... This is a bad practice altogether, since Cr86 is perfectly capable of loading+rendering that site; to circumvent their block, just spoof a current Cr version

 --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36"

... and Bob's your uncle: 

foPlOBm.png

... Might I also add that the page has a sub-optimal web design, not fit for desktop browsers and without any consideration for older, low on resources, hardware :angry: (e.g., it contains in its top part a constantly animating huge video/gif that consumes far too many CPU cycles on OSes without native H/W decoding, via GPU) ...

Apologies for the rant, cheers and best wishes :) ...

Edited by VistaLover
Posted
3 hours ago, VistaLover said:
--user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36"

127th version isn't released to public, yet.

Posted (edited)
19 minutes ago, VistaLover said:

They outright block :realmad: Chromium 86

360Chome 13.5, Windows 10, works here (without changing user-agent).Screenshot_19.jpg.f6ec966bbf14cd67f9ab22f343455eea.jpg

Edited by 66cats
Posted (edited)
31 minutes ago, Dixel said:

127th version isn't released to public, yet.

... But it did work in my posted test; FWIW, 127 just made it to the Windows BETA channel

https://chromereleases.googleblog.com/2024/07/chrome-beta-for-desktop-update.html

The emphasis on my previous post was on "current Cr version", I didn't specify a Cr channel, did I? 

(... Why is it my distinct impression you just posted with an intent to discredit me? Please, don't answer, since I won't answer back myself...)

@66cats: I don't know what to tell you :dubbio:, with the default Cr86 UA I get this (Vista SP2 x86): 

 M4UV9U0.png

Edited by VistaLover
Posted
4 hours ago, Dave-H said:

Could someone using 360Chrome please try this site for me?

www.bbcpa.org.uk

Did you intend to link to an ht-tp instead of to an ht-tpS?

Other than that, it would not load for me in my default setup for v13.5.1030 either.

But DOES LOAD when I use my default alternate UA - which is Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36

Generally speaking, whenever I bump into a site that does not work (and if I remember to change the UA at all!), I DROP TO AN EVEN OLDER v77 THAN TO TRY "NEWER" OR "MOST RECENT" UAs.

And that works in this case too, the site LOADS WITH A V77 UA.

Posted
4 hours ago, VistaLover said:

... But it did work in my posted test; FWIW, 127 just made it to the Windows BETA channel

https://chromereleases.googleblog.com/2024/07/chrome-beta-for-desktop-update.html

The emphasis on my previous post was on "current Cr version", I didn't specify a Cr channel, did I? 

(... Why is it my distinct impression you just posted with an intent to discredit me? Please, don't answer, since I won't answer back myself...)

@66cats: I don't know what to tell you :dubbio:, with the default Cr86 UA I get this (Vista SP2 x86): 

 M4UV9U0.png

Wrong again, Moneypenny. :)(from Bond with T. Dalton)

I've only assumed the site probably didn't know whether it should block that unknown version and let you in. I never wrote I had doubts it let you in, your "distinct impression" is better be called distinct overimagination. And be careful with your thoughts/wishes, some day may come true. The fact Chrome 86 works for points out to Client Hints engaging on Windows 10. 

Posted
5 hours ago, 66cats said:

360Chome 13.5, Windows 10, works here (without changing user-agent).Screenshot_19.jpg.f6ec966bbf14cd67f9ab22f343455eea.jpg

I've encountered many modern sites do let you in with old browsers, but only if you live in a first world country with a clean IP. Twitter had been  a good example, members had troubles with Twitter's feed on Chrome 86, while Dave_H and I - hadn't.

Posted (edited)
8 hours ago, Dixel said:

The fact Chrome 86 works for points out to Client Hints engaging on Windows 10.

Wrong.  Their is no Client Hints in 360Chrome v13.5.  And Win10 doesn't change that fact.

At least, not in my releases.  Do not recall if they existed "upstream".

image.thumb.png.2eb48f45306164c872d78113cec20bf0.png

Edited by NotHereToPlayGames
Posted

Thanks all, the user agent modification has indeed fixed it.
:thumbup
Very bad design though for it to just not load with the original version.
Most incompatible sites put up a page saying that you need to update your browser.
Doing what they were doing just looks lake some other type of fault.
:yes:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...