Standards Compliance To-Do List

We must ensure that as a HTTP and FTP client, Wget confirms to the IETF standards as best as possible. The best way to do so would be to have a bunch of tests, each testing for a compliance to a certain rule in the IETF standards documentation. There are multiple standards available, for e.g. RFC 2616 for HTTP/1.1, RFC 6265 for Cookies, RFC 6266 for the Content-Disposition Header and so on.

The IETF Standards documents define the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

• "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL". These keywords should be interpreted as defined in RFC 2119

Each error reported here should have a corresponding bug report filed on Savannah.

MUST, REQUIRED, SHALL Errors

Highest Priority. These errors must be fixed ASAP.

MUST NOT, SHALL NOT Errors

Highest Priority. These errors must be fixed ASAP.

SHOULD, RECOMMENDED Errors

Important. We must discuss these issues and take a call on whether we want to conform to these or not.

SHOULD NOT, NOT RECOMMENDED Errors

Important. We must discuss these issues and take a call on whether we want to conform to these or not.

MAY, OPTIONAL Errors

These are the least important. Should look into them briefly and decide whether the feature is interesting or not.