Metalinks Code

The HASH command is meant to be used for files transmitted in Image
type mode (TYPE I) and Stream transfer mode (MODE S). The returned hash
MUST be calculated over the raw octet data of the file irrespective of
the selected data type, transfer mode or any other state affecting the
transfer. In other words, if a client were to download a full file using
TYPE I and MODE S and were to calculate the hash on the received octet
data, it would be identical to the hash returned by HASH.

add TT & PP :)

security vulnerability fix

security vulnerability fix

updates

fix for when socks proxy is set in windows

Thus, a publisher can choose weak or strong cryptography, and a
Metalink Processor SHOULD normally accept that. There are potential
applications where the Metalink Processor chooses to reject weak
cryptography, but that is not envisioned as the common use case.

Note that the "metalink:size" element MUST override the actual content length of the representation as reported by the underlying protocol, and those that do not match MUST be discarded by Metalink Processors.

Revert to original:

However, many implementers do not use it because signed XML documents enclosed in other XML documents have their signatures broken.

attempting to improve the language in some places, to make it clearer