Alberto, that is totally unnecessary. No one was wrong - save perhaps the Safari development crew. What happened was the result of a four part bug.

1. Since OS X 10.3.6 Safari's increased its timeout from one minute to ONE YEAR.
2. Users upgrading from Tiger to Leopard experienced corruption of the keychain.
3. When Safari couldn't read the keychain it would incorrectly think it had not reached the site - result: keep hammering away with thousands of hits in a minute or two.
4. Another bug caused Safari to loop out of control after a few minutes and crash.

It's all documented here and it occurs on upgrades and when accessing site URLs that require authentication.

http://rixstep.com/2/4/20080516,00.shtml

As far as we know this has not been fixed by Apple. On the other hand the cure is easy: simply remove the corresponding entries in the keychain and log in again, this time submitting username and password.

The 'one year timeout' does remain what we know in Safari.

This was about half a year ago; it was a panicky time for all. If you don't have our tools then run netstat in a loop when using Safari in this fashion; if you see a sudden blizzard of connections then quit Safari and take the above steps.

Cheers.