Hello

I installed the API of enom, using mozilla, but I am starting perfectly session with mozilla, but with Internet Explorer, not is starting session, I dont know which is the problem,

Could you say me which is the problem?

My site is: dominatic.com username test password test

Regards

working just fine here using IE

Hi

umm, then seem be, than the problem is Internet Explorer, though, I re-installed the Internet Explorer and the problems are go on, also set the privacity at low for my IE, my IE have many bugs, and spywares, also I ran Ad-aware Professional and the zone alarm, but then, should I will format my hard disk?

Also is very strange, In both browser (IE, Mozilla) when I write a domain in the search box, in the API of Enom, for example: dominatic, say:

Congratulations! The domain name:dominatic.com is available!
Register it now by clicking here!

When this is false, because is my domain and for example with webhostingtalk

Already registered We're sorry, the domain name webhostingtalk
has already been registered.

Also when I do log-out it say:

Warning: Wrong parameter count for session_destroy() in logout.php on line 27

Warning: Cannot modify header information - headers already sent by (output started at logout.php:27) in logout.php on line 29



This is a problem by destroying sessions, and the Internet Explorer haven´t blames

Sorry, but The API of ENOM, have a little of bugs

Regards

you are using resellertest.enom.com try kuwaitnet.* it shows some are available :)

It looks like a coding issue on your end. Works fine for me

If you change your error_reporting level to not report warnings those errors wont show up.

Also, you actually have to (as in the instuctions) lower your error repoting becuase of a bug when communicating between linux / IIS.

An EOF occured but the SSL "close_notify" message hasn't been sent, so PHP displays the error. This will happen any time a linux / non IIS machine contacts an IIS server using SSL.

Warning: fread(): SSL: fatal protocol error in /home/august7/public_html/dominatic/include/EnomInterface_inc.php on line 112

If you change it to not display warnings (or in htaccess change it to 21 or possibly even 81) most of these errors will no longer display.

So it does seem this is more a client side issue vs enom's system

Yes, this actually occurs in PHP itself, and can be reproduced anytime by making a SSL communication to an IIS server - this is not dependant on enom.

http://bugs.php.net/bug.php?id=23220