Daniel wrote:
> On 21/07/2016 3:15 AM, Arnie Goetchius wrote:
>> WaltS48 wrote:
>>> On 07/20/2016 11:54 AM, Arnie Goetchius wrote:
>>>> Desiree wrote:
>>>>> On 7/18/2016 10:38 PM, Paul B. Gallagher wrote:
>>>>>> Ray_Net wrote:
>>>>>>> Paul B. Gallagher wrote on 19/07/2016 00:59:
>>>>>>>> Ray_Net wrote:
>>>>>>>>
>>>>>>>>> So the best default User agent string could be:
>>>>>>>>> : Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101 SeaMonkey/2.38
>>>>>>>>> same as Firefox/41.0
>>>>>>>>>
>>>>>>>>> then it will be recognized as FF by the bad sniffing method and
>>>>>>>>> recognized as SM by everybody.
>>>>>>>> You're thinking like a human being, silly!
>>>>>>>>
>>>>>>>> Some sniffers reject a UA string that contains "SeaMonkey" even if it
>>>>>>>> also contains "Firefox." That's why the solution in this thread worked
>>>>>>>> -- because Chase's sniffer is that stupid. You have to pretend to be
>>>>>>>> Firefox AND pretend not to be SeaMonkey.
>>>>>>>>
>>>>>>> I just thinked that the sniffer will only use the last "word" which is
>>>>>>> in this case "Firefox/41.0" instead of in the normal UAstring the last
>>>>>>> "word" is "SeaMonkey/2.38"
>>>>>>>
>>>>>>> So could be better to have the default string this:
>>>>>>> Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101 SeaMonkey/2.38 same
>>>>>>> as Firefox/41.0
>>>>>>> instead of this:
>>>>>>> Mozilla/5.0 (Windows NT 6.1; rv:41.0) Gecko/20100101 Firefox/41.0
>>>>>>> SeaMonkey/2.38
>>>>>>>
>>>>>>> Is my idea a bad idea ?
>>>>>> If it works, it's good; if it doesn't, it's bad. Only a Chase customer
>>>>>> can tell us. I can't log in because I don't bank with them. My bank is
>>>>>> fine with SeaMonkey.
>>>>>>
>>>>> For me, as a Chase customer, SeaMonkey cannot be in the string at all. I
>>>>> have
>>>>> Windows 8.0 Pro and am using User Agent Switcher extension and chose this
>>>>> string: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:40.0) Gecko/20100101
>>>>> Firefox/40.0. It works fine.
>>>> I logged into my Chase account (with Firefox, of course) and used their
>>>> Secure
>>>> Message center to send the following message. They say they will be back
>>>> to me
>>>> in one business day. I am looking forward to what they say. Probably "We no
>>>> longer support Netscape" :-)
>>>>
>>>> Why Won’t Chase Accept Seamonkey as a Legitimate Browser?
>>>>
>>>> The original and most popular internet web browser in the early 1990’s was
>>>> Netscape Navigator. When the ability to send and receive emails was added
>>>> to
>>>> the
>>>> Netscape Navigator’s capabilities, the browser’s name was changed to
>>>> Netscape
>>>> Communicator. Netscape Communicator was eventually taken over by the
>>>> Mozilla
>>>> Foundation where in addition to Netscape Communicator, Mozilla produced a
>>>> browser only without email capability and called it Firefox. At that time
>>>> Netscape Communicator was renamed Seamonkey. In essence, Seamonkey is a
>>>> direct
>>>> descendant of the original Netscape browser. It continues to be
>>>> maintained by
>>>> Mozilla and the browser portion of Seamonkey works the same way as FireFox.
>>>>
>>>> The problem is that when the Chase web software looks at the browser being
>>>> used
>>>> as defined by the User Agent string shown below, it accepts the User Agent
>>>> string from Firefox but rejects the User Agent string from Seamonkey. The
>>>> only
>>>> difference between the two User Agent strings is that the one from
>>>> Seamonkey
>>>> adds “Seamonkey/2.40” at the end. Other than that, they are both the same.
>>>> User
>>>> Agent strings will also vary depending on the operating system used by the
>>>> computer. However, the common part of the User Agent string,
>>>> “Gecko/20100101” is
>>>> always present no matter what operating system is being used.
>>>>
>>>> I hope that the people who run your website will once again accept the
>>>> users of
>>>> the descendant of the original web browser now called Seamonkey as do the
>>>> other
>>>> major financial institutions such as American Express, Wells Fargo, Charles
>>>> Schwab, etc, etc
>>>>
>>>> User Agent String Samples for Firefox and Seamonkey
>>>>
>>>> Firefox
>>>>
>>>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>>>> Firefox/43.0
>>>>
>>>> Seamonkey
>>>>
>>>> Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101
>>>> Firefox/43.0
>>>> SeaMonkey/2.40
>>>>
>>>>
>>>
>>> Actually it is SeaMonkey and not maintained by Mozilla, but the SeaMonkey
>>> Council, a small group of dedicated volunteers, that has lost some of its
>>> long
>>> time contributors, just like Thunderbird.
>>>
>>> Nice letter though.
>>>
>> Thanks for the correction on SeaMonkey Council. If my communication with
>> their
>> message center doesn't work, I will send a copy of the above to Dr Gavin
>> Michael, Chief Technology Officer at Chase at their NY HQ.
>>
> And if I were to be picky picky, I would state that the correct User Agent
> string for SeaMonkey 2.40 was ...
>
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 SeaMonkey/2.40
>
> If you go to Edit->Prefs->Advanced->HTTP Networking, you can select to
> "Advertise Firefox Capability" in the User Agent String, which adds the
> Firefox/43.0 bit.
>
> And Arnie, if you do actually send in a real "Pen and Ink" letter, it might
> also
> be worthwhile mentioning that other browsers, which currently cannot get to
> the
> Chase site because of the incorrect sniffing, could/would also work if Chase
> sniffed for the Gecko process, rather than for a particular Browser Name.
>
Thanks for the ideas. Sniffing for Gecko is the key. Since Dr Michael (Chase
CTO) received his PhD in Computer Science from Australian National University,
I'm sure he will have no trouble in understanding the concept. :-)
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
