我正在尝试使用Wget如下：
wget -O- --debug
--header=Content-Type:text/html
--post-file=index.html
http://localhost/www/encoder.ashx
HTML发布到的URL是一个使用ASP.NET实现的Web应用程序端点。服务器回复为100（继续）响应，Wget只是停在它的轨道上，而不是继续接下来应该遵循的真实响应。
是否可以以某种方式告诉Wget使用100（继续）响应，或者这是该工具的一些众所周知的限制
笔记：
I noticed that Wget never sends the
Expect: 100-Continueheader so technically the server should not be issuing a 100 (Continue) response.UPDATE: Looks like this is possible, as per §8.2.3 of RFC 2616 (Hypertext Transfer Protocol -- HTTP/1.1):
An origin server SHOULD NOT send a 100 (Continue) response if the request message does not include an Expect request-header field with the "100-continue" expectation, and MUST NOT send a 100 (Continue) response if such a request comes from an HTTP/1.0 (or earlier) client. There is an exception to this rule: for compatibility with RFC 2068, a server MAY send a 100 (Continue) status in response to an HTTP/1.1 PUT or POST request that does not include an Expect request-header field with the "100- continue" expectation. This exception, the purpose of which is to minimize any client processing delays associated with an undeclared wait for 100 (Continue) status, applies only to HTTP/1.1 requests, and not to requests with any other HTTP- version value.
cURL has no problems with such a transaction. It send an
Expect: 100-Continueheader and continued with 100 (Continue) response on to the real one.
有关更多信息，以下是上面显示的调用中事务的完整调试跟踪：
Setting --post-file (postfile) to index.html
Setting --header (header) to Content-Type:text/html
DEBUG output created by Wget 1.10 on Windows.
--13:29:17-- http://localhost/www/encoder.ashx
=> `-
Resolving localhost... seconds 0.00, 127.0.0.1
Caching localhost => 127.0.0.1
Connecting to localhost|127.0.0.1|:80... seconds 0.00, connected.
Created socket 296.
Releasing 0x01621a10 (new refcount 1).
---request begin---
POST /www/encoder.ashx HTTP/1.0
User-Agent: Wget/1.10
Accept: */*
Host: localhost
Connection: Keep-Alive
Content-Type: text/html
Content-Length: 30984
---request end---
[writing POST file index.html ... done]
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 100 Continue
Server: ASP.NET Development Server/9.0.0.0
Date: Wed, 24 Sep 2008 11:29:17 GMT
Content-Length: 0
---response end---
100 Continue
Closed fd 296
13:29:17 ERROR 100: Continue.