A bunch of points that need looking into and discussions as we implement better RESTful scripting support in Wget.
- Saving Content-Location Headers in 2xx Responses to POST Requests: According to the latest HTTPbis Draft, a 2xx Response to a POST Request may contain a Content-Location Header that either points to the newly created/modified resource as a direct/indirect result of the Request. This resource can later be retrieved through a GET request. If we are improving RESTful scripting support in Wget, this is an important point to consider.
- Re-trying of non-idempotent methods: Wget should not attempt to retry non-idempotent methods in case of connection failures unless explicitly told to do so by the user. This is important since, otherwise one takes the risk of corrupting server side data in the case that the response could not be received by Wget for any reason.