> > This server doesn't seem too conformant... «The methods GET and HEAD MUST > be supported by all general-purpose servers. All other methods are > OPTIONAL; ... » -- > https://tools.ietf.org/html/**rfc2616#section-9.4<https://tools.ietf.org/html/rfc2616#section-9.4> > If you wanted to work around it, I would go with 3 (but is it worth?). > The accepted methods (GET, POST) are given in the error response, there's > no point in sending an OPTIONS first for this exceptional server. > > That is extremely true. According to RFC2616, any general-purpose server MUST respond with the exact same headers to a HEAD request as to a GET request.
Also, if the server does not support HEAD requests, I doubt it will respond correctly to OPTIONS. Although, if it isn't too much to tinker with, I would prefer if Wget could smartly handle such a situation. -- Thanking You, Darshit Shah
