OK, I've now implemented a very silly check, but at least it will
cover most cases of usage. Setting the cookie for a second-level
domain (e.g. ".foo.bar") is allowed if:
+ The top-level domain is one of the several recognized ones
OR
+ Its subdomain is more than three characters long.
This m
"monstru" <[EMAIL PROTECTED]> writes:
> this letter is to simply comment you that the new option in 1.8
> version, --limit-rate, doesn't appear in the man page... it seems
> that someone forgot to put it in the page... or not.! :)
Yes; it's a simple oversight.
It will be documented in the next
Yes -- Wget versions up to the latest one in CVS can get suck in
connect() if the remote server is sufficiently catatonic. In the
latest CVS sources the `-T' timeout also covers the timeout of
`connect'.
ScanMail for Microsoft Exchange has taken action on the message, please
refer to the contents of this message for further details.
Sender = [EMAIL PROTECTED]
Recipient(s) = [EMAIL PROTECTED];
Subject = Hi,meeting notice
Scanning Time = 04/20/2002 11:51:01
Engine/Pattern = 6.150-1001/267
Action o
