powernotebooks.com compal HEL80

i didnt know where to post this, but i was looking at to buy the compal HEL80 and all of a sudden when i click add to cart, a pop-up appears saying: something like: "Domain Error" "You have tried to make a connection with powernotebooks.com and and certificate. . .blah blah blah. . . " "someone may be trying to intercept your information".

Now im not scraed oh.. hacker blah blah, i heard of powernotebooks great customer support and all, and im wondering why this is popping up. Should i continue into my checkout or not?

http://powernotebooks.com/product.php?itemId=1503

i click on the HEL 8:15 Ultra, and configured and and clicked 'checkout' and this message appeared.

I wanna kno if anyone else has experieneced this problem currently?

 

No, but if you call on the phone you can get a better deal!

 

Definitely give them a call. It's worth it, I promise.

 

x3

"NEWS: CALL US for Special Promotions on PowerPro and Crown Models"

 

That sounds like the generic dialog that comes up when the site's certificate doesnt' check out. Sometimes that happens with legitimate sites on a technicality, and rarely, it means that you're not connected to the site it looks like you're connected to.

Definately call em. It's a good thing to do anyways

 

It must be something with your browser or your system. Our checkout system is working just fine, and our SSL Certificate is current through March of 2008.

 

Hey Donald, I just clicked through myself, and I get the dialog as well. It's complaining that powernotebooks.com doesn't match www.powernotebooks.com

 

So are you saying that when you use http://PowerNotebooks.com instead of http://www.PowerNotebooks.com you get this error?

Have you come back using the www. to get the same result, or does it work when you use www. ?

 

Check your e-mail donald, I sent you some screen shots and information.

 

Got it! Thanks Pyro...we are looking into it now.

 

If I prepend www. to the url, I don't get any error. You probably figured that out by now, though.

 

Ah.. the marvels of the Domain Name System!

 

Well, it isn't really an error it is just a security warning when going from a non secure page to a secure page, and it only appears when you are not using the www. (our SSL Certificate is only for //www.PowerNotebooks.com, not //PowerNotebooks.com). When you read (what a concept ) what it says you realize that it is trying to protect you from being directed to a site that you don't want. In today's world that can be a helpful thing.

All you have to do is click through it and the page loads.

There is nothing we can do about it from our side, that security protection is being built in to all the browsers these days in an attempt to increase security while surfing.

 

I suppose "warning" is a lot more fitting of a word for it. I tend to not be too choosy with my words, since it seems irrelevant most of the time.
When helping people with computer trouble, I've noticed the trend seems to be to not read anything. I ask them about the contents of dialog boxes, and I consider myself lucky if I can get "red... circle... with x!". (Picture controted facial expression and hair standing out in all directions)
... I've even sent emails with specific instructions and a file, and then gotten phone calls asking what to do with the file. Go figure.

Just from curiosity, how does that certificate system work, from your end? I've seen that error a few times before, where www.site.com would be registered, but secure.site.com wouldn't be, or something like that.

 

I know on the websites I admin (well, used to) I wrapped certificates to activex installers so that customers could run utilities right from my website like they are installed locally. You normally go through a rather information "request" for a certificate, where you provide alot of information about the information you want the cert for. One of them is the website url so that customers know where the cert is from (read: who it's for). After your request is accepted (they verify its unique to there system, sometimes they check out your site to verify its legal content), you get a certificate file that you use a utility to wrap it to your content sort of like zipping a file. Then you put the file for access on an http server just like any other and the browser does the rest.. Depending on who made your certificate, sometimes a client must install the 3rd party certificate to get the system to stop whining. (This is why you pay for these certs normally, so that M$ will include the darn master cert with there browser so customers are blind the the process)