Qwest Freezing

[kitokatlin]

I have been having terrible problems with qwest.com. Most pages completely freeze the browser and sometimes it gives an XSS problem. It is to the point where I have to end task for mozilla when I attempt to go to qwest.com most of the time. I believe that it is when the page is loading the "chat with customer support" link. This is driving me crazy!

[therube]

URL: http://www.qwest.com/

Sure is something screwy (as in like not much happening) once you Allow qwest.com.

Code: Select all

Error: 'NoScript aborted redirection to https://www.qwest.com/qcms/qCmsRepository/Global/Javascript/Base64.js' when calling method: [nsIChannelEventSink::onChannelRedirect] = NS_ERROR_XPC_JS_THREW_STRING

Don't ask me why I got that error - once.
Trying to get it again, the page did finally load.

Base64.js is "http:", but when you load it, it is "https:".
Some of the other JavaScript links they use are https too.

If you remove NoScript, there is still the same sort of delay with qwest.com.

Even IE struggles with it.

About the only thing you can say, is that it loads nicely with NoScript blocking JavaScript on the site .


Good thing they're only a fly-by-night entity .

[therube]

Today, different computer, different ISP & qwest loads much better.

Though this did turn up:

Code: Select all

[NoScript] ClearClick skipping, same site parents for http://www.qwest.com

Not that I know what it means?

[Giorgio Maone]

Not that I know what it means?

Simply that you left noscript.consoleDump at 4096 (ClearClick logging).

[therube]

.

And between the time I posted the above post & now, they have totally revised their site layout.

No they didn't. Kind of.
What page you get depends on your User Agent string setting.
Further, they must be using a cookie to record that. So once set to one style, it stays that way until you clear cookies.

What page you get depends on your User Agent string setting.

Maybe?
If I spoof SeaMonkey 1.1.18, to be Firefox/3.0 & get a different layout.
Clear cookies & spoof it to Firefox/2.0 & I get the same layout as I get in SeaMonkey 1.1.18.
Clear cookies & spoof back to Firefox/3.0 & back to the alternate layout.

But in SeaMonkey 2, doing the same always gives me the alternate page regardless of the UA setting.
So maybe they are also checking the Gecko version number?