sign in using Netscape very SLOW

micklerlop

I have an authentication system. below is my code:

function checkSignIn($myEmail, $myPassword) {
$check = "select name from person where email = '$myEmail' AND password = password('$myPassword')";
$result = mysql_query($check);
if(!mysql_num_rows($result)) return 0;
else {
$query_data = mysql_fetch_row($result);
return $query_data[0];
}
}

...bla bla here...

session_register("myEmail", "myPassword");
$myName = checkSignIn($myEmail, $myPassword);
session_register("myName");
if(!$myName) {
session_unregister("myEmail");
session_unregister("myPassword");
session_unregister("myName");
echo "$myName and fail";
} Else {
echo ("welcome $myName");
}

I am testing on my IIS5, localhost. It works perfectly, nothing wrong at all. However, when signing in with Netscape, it takes a while for it to response.

First I thought there was a problem with querying my table or the database structure that made it slow. In fact, it's not because when just query like "select * from..."
It's also fast in Netscape. Just the sign in process that is slow. By the way, i have tested with NS 4.76 and 4.78.

Please advice,

mick

mithril

Is this on Win2K? If you take focus away from the Netscape window (ie. click the taskbar, etc.) does the process speed up? If so, it's probably a problem in the form submission, not the actual authentication algorythm.

Check the DNS suffix's for all your networking connections (dialup and network cards) and make sure that the entry is a valid domain name. I had the same problem with form submissions on NS 4.7x (running Apache and IIS) recently. I believe that Win2K tries to do a host lookup on Netscape submissions, and borks if it can find the host. HTH.

-geoff

micklerlop

Thank you for your reply.

Yes I am on Win2k. I tried what you told but there is nothing wrong with it. i mean the process didn't speed up at all.

One thing I noticed, I tried to sign in from a computer, using NS 4.76, that is on another network than my server. The sign in process was as fast as when using IE on the same machine. So the problem only exists when using NS on the server maching.

Any idea for this?

mithril

Then we've reached the extent to which I can offer ideas🙁 The situation is exactly the same as the one I experienced. It was more of a fluke that I fixed it than anything else (I came across the incorrect DNS suffix because of a totally different issue, but NS worked after changed the suffix).

-geoff

mithril

Possible solution here. Mozilla announced the release of NS 4.79 today.

The changelog:

   Improvements accessing subfolders under the Inbox on certain mail servers.
   Performance improvements when accessing pages with nested tables and style sheets.
   Win2K Only: Improved performance when using certain pages with JavaScript and document.write.
   Mac Only: Sizing when printing problem on certain Epson printers fixed.
   Mac Only: Composer now retains the default URL of the edited document.
   Unix Only: You can now add multiple personal address books.
   Improved support for dual processor machines.
   Win2K Only: Improved Performance when contacting a server on the same machine.
   Fixed incompatibilities which caused Communicator to quit unexpectedly while viewing certain web sites.
   Upgrades to Components: Netscape AOL Messenger version 4.3 (Mac only)

The link:

  http://mozillaquest.com/News01/Netscape_4-79_released_Story01.html

HTH.

-geoff

micklerlop

Thank you

bparish

I don't know if this is related but I found that changing the ServerName directive in Apache to 127.0.0.1 made a significant difference to NS 4.78 performance:

ServerName 127.0.0.1

Hope this helps.

Ben