You should try to validate the page to see what a mess it is.
And your DOCTYPE is not valid.
Bye, TMTisFree
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
He means that the HTML code used on the page is invalid and contains a lot of errors.
And that the html dialect that the page claims that is using does not match what it is actually using.
Both which means that a browser trying to render it has to do a lot of guesswork to decode it.
The index page on that site contains 52 errors (html violations) and 2 warnings. Which is a bit embarrassing to the web developers who made the page. Especially considering how easy it is to properly validate html these days.
And no, opening a web page in a browser is not a proper way of validating.
Well this mean that I will never be able to use OWB to make my account transactions because I'm sure that they won't fix the errors since I'm surelely the only one that is using an Amiga and I don't use on of the WEB browsers recommended.
Well this mean that I will never be able to use OWB to make my account transactions because I'm sure that they won't fix the errors since I'm surelely the only one that is using an Amiga and I don't use on of the WEB browsers recommended.
If there would be a problem with the contents you could tell them you are using another WebKit browser, for example Safari or Google Chrome, but OWB doesn't get that far. I guess it's a SSL related problem, but since OWB doesn't display any transfer errors I'll have to build a special debug version to find out what exactely the problem is.
If this is not too much trouble I'll appreciate you find the exact problem...
As expected it's a SSL problem ("SSL certificate verify result: self signed certificate in certificate chain (19)"). To access such insecure sites with self signed certificates in OWB until the next reboot use
SetEnv WEBKIT_IGNORE_SSL_ERRORS 1
in a shell before starting OWB, or if want to make it permanent use
Well this mean that I will never be able to use OWB to make my account transactions...
From the sounds of it, that is a very good thing!
First of all, the HTML is garbage so there may be ways for a hacker to sneak in and spoof it or similar. Second, their SSL is broken which is insane for any financial institution and invites thieves to steal your private information.
Feel free to pretend that web site is secure if you want to but don't complain to us when somebody steals your money and/or takes your identity.
Sorry to bump this thread, but I'd like to know if OWB is using AmiSSL for its SSL transactions or if it's using a builtin SSL version ? I ask it because I have found that OWB is unable to login into any https url I've come to, whereas AWeb is fine accesing them (so AmiSSL works fine), in fact I even searched on google an HTTPS test page and tried to load it in OWB without success (so this should not be a problem specific to my bank's website which is bytheway Cr?dit Mutuel at https://www.creditmutuel.fr/cmlaco/fr/) the page starts to load and then nothing comes, the text load jauge at the bottom right stays on 0 ? So is there something to configure somewhere (without compromising security like the IGNORE_SSL_ERROR above) ?
Sorry to bump this thread, but I'd like to know if OWB is using AmiSSL for its SSL transactions or if it's using a builtin SSL version ?
Builtin SSL.
Quote:
I ask it because I have found that OWB is unable to login into any https url I've come to, whereas AWeb is fine accesing them (so AmiSSL works fine), in fact I even searched on google an HTTPS test page and tried to load it in OWB without success (so this should not be a problem specific to my bank's website which is bytheway Cr?dit Mutuel at https://www.creditmutuel.fr/cmlaco/fr/) the page starts to load and then nothing comes, the text load jauge at the bottom right stays on 0 ?
The page is working here. If you used AmiUpdate for updating OWB and skipped some versions it could be that Resources/curl-ca-bundle.crt in the OWB directory is missing, copy it from DEVS: to the OWB Resources directory.
Okay, thank you for the tip it was the problem. Can't you check in the AmiUpdate install script if the certificate file is there and either move the one from DEVS or copy a new one ? Eventually displaying a warning message might do the trick too.