CD is unsupported by T-Mobile because of incompatibility?

Within the last few months or so, T-Mobile’s site started not allowing logging in with CD, but not with a specific error, such as about supported browsers. I had to find out from their customer support that CD wasn’t supported.

As explained on a T-Mobile forum:

“With all the other things they [Comodo] put into it for supposed securitys sake compliccates allot of other standards used by most online services and would need to have different versions to be compatible. . . . I have used the dragon browser before and I also found compatibility issues with etrade, 2 of my banks among other things.”

Is there any valid reason for such incompatibility?

From my understanding, the differences between Chrome/Chromium and CD at least somewhat relate to this list:

But are there perhaps other fundamental changes?

It would be nice if such technical details were listed upfront in the product info, and I know I’m not alone in this desire.

I would personally call that bullrubbish*, but of course I don’t know. If they can’t make their webpage work with security that means they are using insecure contents or means to go by. I have not encountered any webpage that has been incompatible with CD and I’ve logged into my bank etc.

So in my opinion, any reason they have for not being compatible with CD is because they are too lazy to get off their ■■■ and get their security right. A company to avoid in my opinion.

Disclaimer or whatever: This is just my opinion and all of it lacks any actual facts so don’t take my comment as truth since I might be dead wrong.

Hi ParticleMan,
Have you tried any setting changes in CD to see if it helps, in particular try disabling Do not allow websites to know where you came from (suppress HTTP referrer header) if you have it enabled.
Found under privacy in advanced settings.

Haha, this option caused quite a few problems when I accidentally turned it on in Chrome =P So I wouldn’t say that it’s specific to Dragon. However, is it enabled by default?

Hi SanyaIV,
It is disabled by default, but a lot of people enable it hoping it will add to their privacy.
Quote taken from Dragon help,

[b]Do not allow websites to know where you came from (suppress HTTP referrer header)[/b]. The disable referrer option stops website owners from knowing which URL (website) you visited immediately before arriving at their website. [b]This option is disabled by default[/b]. Enabling this option will immediately stop referrer information from being passed to websites that you visit.

Bingo! Thank you so much! And yes, I did think it would add to my privacy… it sounds so innocent. :wink:

SanyaIV, I agree. The claim sounds like utter poppycock. It will be fun to point that out and that the real problem was just a setting.

I think it should be noted that it can break websites like banks etc. =)

Oh? Why is that? CD’s heightened security and/or other reasons?

I meant within the help file it should be noted that when you enable “Do not allow websites to know where you came from (suppress HTTP referrer header)” it could break websites like banks etc since they often rely on what website you came from. Which was also the problem with T-Mobile if I didn’t get it wrong.

Disabling it shouldn’t break sites at all and the only security issue I see with it is that any webpage can see what page you visited before the page that you are at. So lets say I visit and then click a link to, can see that the previous page was At least that is how I understand it.

Some people do get the feeling of added security by enabling Do not allow websites to know where you came from (suppress HTTP referrer header) . Wrong.
In some cases enabled will give better privacy but not better security, but it can break sites.

Some sites need to know where the page request originated from, this can be added security from the site.
Example of why: On a site that has a login function, this site might need to know that the request for the login page was indeed requested through their own channels and not from some outside location which could pose a security threat.
Some sites consist of two login pages to complete login the first consisting of username/password then continue to the next page to answer your secret question then submit login.
If the 2nd page didn’t know you came from the first it would fail.
These are just examples and there are plenty of other scenarios where a requested page will need to know where the request come from.

Are you more private if you enable Do not allow websites to know where you came from (suppress HTTP referrer header), possibly slightly in some cases.

Are you more secure from Malware attacks if you enable Do not allow websites to know where you came from (suppress HTTP referrer header), simply no.
Kind regards.