USPS.com Browser Check ....

[Wish You Were Here]

It appears there may be an issue with some using the USPS.com websites:

https://www.usps.com/browser-check/

Is it being dealt with?


(Side note, this forum page took several minutes to load).

[DanRaisch]

Which browser are you actually using? Your User Agent string reports Firefox version 56 but you posted to the SeaMonkey Support Forum. If you are actually accessing that site using Firefox 56, they are telling you to update to the current Firefox version, 59.0.2, to overcome their browser check issue.

[Wish You Were Here]

SM 2.46 Build identifier: 20161213183751

Don't know why that other is there unless it was something I did trying to get Yahoo Mail to work better, which it still doesn't.

[DanRaisch]

Change the 56 to 59 and try those sites again. Version 56 of Firefox is now considered obsolete and unsafe to use.

[Wish You Were Here]

Good news — your browser is up to date.

You can continue to access all USPS.com features with your current browser version.

Thank you for using USPS.com!


So, it's not really the browser, just some numbers?

Why do we have to spoof SM to get it past sniffers though?

[frg]

> Why do we have to spoof SM to get it past sniffers though?

Ask usps. Only legit if they use some features from later versions. Usually just a stupid check done by people who don't care about alternate browsers.

2.46 is obsolete. 2.49.2 is current. 2.49.3 is in the works but held up by our osx builder failing (hardware related).
Most candidates are done, probably the final and what is there is usable:
https://archive.mozilla.org/pub/seamonk ... es/build2/

[Bozz]

@frg...is there a setting to overide the Firefox/52.0 advertised version or do we just need too use general.useragent.override.usps.com / Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0?

[therube]

The only option SeaMonkey has is to include, or not, the "Firefox/52.0" part in the UA.
So you would have to set (add) the "general.useragent.override.usps.com" Pref.

Code: Select all

get_browser();
function checkingBrowser(){
var bCheck;
 switch(get_browser().name){
	case ("IE"):
		if(get_browser().version>=11){console.log('IE pass');bCheck='pass';}else{console.log('fail');bCheck='fail';}
		break;
	case ("Chrome"):
		if(get_browser().version>=63){console.log('Chrome pass');bCheck='pass';}else{console.log('fail');bCheck='fail';}
		break;
	case ("Firefox"):
		if(get_browser().version>=58){console.log('Firefox pass');bCheck='pass';}else{console.log('fail');bCheck='fail';}
		break;
	case ("Safari"):
		if(get_browser().version>=10){console.log('Safari pass');bCheck='pass';}else{console.log('fail');bCheck='fail';}
		break;
	case ("MSIE"):
		if(get_browser().version>=11){console.log('MSIE pass');bCheck='pass';}else{console.log('fail');bCheck='fail';}
		break;
	default:
		console.log('unknown');bCheck='unknown';
		break;
}

Can you imagine, the USPS is going bleeding edge .
(And not to mention, that during this time, till August or so, FF 52 ESR is still going to be a supported [Mozilla] browser.)

[Bozz]

Thanks therube.

[Wish You Were Here]

The question will be if the site is functional after the first of May by using these steps. Or maybe only some portions will be affected.

YahooMail really doesn't work well at all, so maybe USPS won't either. Then what do we do?

[Anonymosity]

2.46 is obsolete. 2.49.2 is current. 2.49.3 is in the works but held up by our osx builder failing (hardware related).
Most candidates are done, probably the final and what is there is usable:
https://archive.mozilla.org/pub/seamonk ... es/build2/

The candidate for MacOS is dated Apr. 11, so the failure must be very recent, or there is a different machine for final releases.

[frg]

> The candidate for MacOS is dated Apr. 11, so the failure must be very recent, or there is a different machine for final releases.

No this one is ok. At least the de language pack and the release is missing. This is all what is holding the release up right now I think. The mac needs to be rebooted with the big red switch or reset button. When it is back it works for some time and then goes offline again. Some sort of hardware failure. The whole Mozilla based SeaMonkey infrastucture will be scrapped in Q3 or Q4 so we need our own. They will not move our builders. TB was more integrated and was allowed to migrate to taskcluster but needs to do its own infra later. Mozilla = Firefox only these days.

FRG

[Wish You Were Here]

Mozilla = Firefox only these days.

FRG

That's not good.

[mrmazda]

"Not good" was incepted more than 12 years ago, whenever it was that it was announced that Mozilla Suite was being replaced by Firefox as the project's Flagship. As we've seen from the loyalty of SM users and its few remaining committed devs, a suite has more holding power than a mere browser, making it harder for Joe Public to "switch".

[LordOfTheBored]

"Not good" was incepted more than 12 years ago, whenever it was that it was announced that Mozilla Suite was being replaced by Firefox as the project's Flagship. As we've seen from the loyalty of SM users and its few remaining committed devs, a suite has more holding power than a mere browser, making it harder for Joe Public to "switch".

In fairness, Joe Public switched long ago. From Internet Explorer to Firefox.
And they've switched to Chrome since then.

But there continues to be a small subset of users that are of a more technical mindset, who choose their software based on more than what ad they saw most recently, and who have strong opinions on what a browser is supposed to do(or perhaps more importantly, NOT do). Unfortunately, websites are largely developed by and for the less technical mindset, so... browser sniffing even if they're only serving plain text.