ID: 24028 Comment by: p at aol dot com Reported By: xiongwei at aerafront dot com Status: Closed Bug Type: CGI related Operating System: win32 only PHP Version: 4.3.2 New Comment:
Moving to 1and1? Good luck. I had a bad expreience with 1and1. I used to recommended 1and1 and I thought it’s big company and the service and support should be better. Unfortunately, i learned from the hard way. 1. If you tranfer your domain, chances are you will have to wait for days. The status shown on the panel does not reflect the actual status. For example, if the status is “Ready” and you try to set the DNS server, the server will fail as the transfer might not be complated eventhough it stated “Ready". The only way you can tell is search the domain via a lookup in whoswho database and see if the transfer is completed. 2. If you trying to setup the DNS server and if the nameserver is not in 1and1 database, you will never be able to set it up. 3. The support is so inexperience that they trying so hard to give answer regardless if it’s right or wrong. The worst is if you call at night where your call transfer to India where those folks don’t even know much about how domain registration works. 4. The package is a very stupid ideas. If you have more than 1 domain and it’s setup in a different contract you have to navigate few pages in order to maintain both domains. The funny part is all the pages are identical. Just wonder if there ever thought about this before creating the site? Well, I have nothing againsts going with 1and1 if you willing to take the risks. As for me, I already moved to others registrar even if I have to pay more as my sites were down for 3 days waiting for the DNS to cache. Most company set the refresh TTL to 24 hours but 1and1 is 72. How stupid it is. Previous Comments: ------------------------------------------------------------------------ [2003-06-24 12:58:38] [EMAIL PROTECTED] Fixed -> closed. ------------------------------------------------------------------------ [2003-06-04 22:24:32] xiongwei at aerafront dot com I wrote a routine "postrawdata.php" for displaying HTTP raw request message. <?php $putdata = fopen( "php://input" , "rb" ); while(!feof( $putdata )) echo fread($putdata, 4096 ); fclose($putdata); ?> It works properly when using a socket program to post something to it. But submitting from a simple HTML below will make it dead, even http headers were not sent back, the behavior of brwoser is just waiting before timeout, I have tested it under IE 6.0 and Netscape 7.0 , any suggestion is appreciate. <body> <form name="form1" method="post" action="postrawdata.php"> <input type="text" name="name" > <input type="submit" name="Submit" value="Submit"> </form> </body> I think PHP does not send correct responding data to browser, or it does not disconnect the HTTP channel, that makes browsers to wait , whereas my socket client do disconnect when finished. Thanks, William Hong ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=24028&edit=1
