How to make msn.com work?

[Peter Creasey]

For msn.com, I use the override stipulating 99.9 and it no longer works.

Can anyone please how to make msn.com work with current SeaMonkey?

Thanks.

[BruceAWittmeier]

I don't know what your override stipulation is, however, this link works for me in seamonkey: https://www.msn.com/

[DanRaisch]

No problem with that site here using version 2.53.14. Have you tried Safe Mode with NO tweaks to the UA?

[Peter Creasey]

Bruce and Dan, thanks so much.

I deleted the user agent override for msn.com and it now is working again.

[Peter Creasey]

[quote="Peter Creasey"I deleted the user agent override for msn.com and it now is working again.[/quote]

This has stopped working and msn.com no longer works.

Any suggestions?

Thanks.

[-Px-]

Define: working.
For me the page is opening, and random news from it too

[Peter Creasey]

After removing the override which was previously advised and was working fine, now accessing msn.com with SM only loads a blank page -- no content.

[v_v]

Peter,

" https://www.msn.com/ " is loading and working for me using SeaMonkey 2.53.16 and my user agent is "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.16".

You seem to have changed your user agent string since your "December 30th, 2022, 9:32 am" post. Back then you were using "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.14". Granted that SeaMonkey has moved on to version 2.53.16 but I am going to guess that you made a modification somewhere. Go to 'Edit -- Preferences -- Advanced -- HTTP Networking'. Is your "User Agent String" set to "Identify as SeaMonkey and advertise Firefox compatibility"? If not, you might want to try that.

v_v

[Peter Creasey]

Is your "User Agent String" set to "Identify as SeaMonkey and advertise Firefox compatibility"? If not, you might want to try that.

Good call.

And, yes, I had changed that at someone's recommendation (Frank's?) to solve access for another site (which site I cannot remember).

In any case, doing what you suggest solved msn.com. I'll just have to wait and see what other site might now starting failing.

Thank you for your welcome assistance.

[v_v]

Peter,

I'll just have to wait and see what other site might now starting failing.

My thought would be that generally it would be better to just allow the basic SeaMonkey user agent string to do its work. When problem sites arise then those are the ones that need a specific user agent override.

v_v

[Peter Creasey]

My thought would be that generally it would be better to just allow the basic SeaMonkey user agent string to do its work.

I don't disagree. The msn.com override worked fine for a long time.

Now, it will be interesting which site fusses about the HTTP override (to SM and FireFox).