- From: Henrik Nordström <henrik@henriknordstrom.net>
- Date: Fri, 14 May 2010 11:52:24 +0200
- To: Joe Orton <joe@manyfish.co.uk>
- Cc: ietf-http-wg@w3.org
mån 2010-02-22 klockan 09:36 +0000 skrev Joe Orton:
'
> Ah, I wasn't clear here: httpd/mod_proxy will, given a request
> containing "Expect: 100-continue":
>
> 1) send the request including the Expect header to the next hop
> 2) generate and send a "100 Continue" to the client
2 there is a clear violation. Intermediaries MUST NOT generate 1xx
responses.
> 3) read the request body from the client and forward it to the next hop
> 4) read the response from the next hop and forward it to the client
>
> So I guess this seems to comply with the letter of 2616 ("MUST forward
> the request, including the Expect header field") but not the spirit:
> that Expect is handled end-to-end, not hop-by-hop.
Err.
Expect is supposed to be handled hop-by-hop but sent end-to-end. There
is severaly MUST NOT forward the request clauses attached to Expect.
1xx responses is end-to-end.
417 responses is used at hop-by-hop Expect processing to signal that the
expectation can not be met if needed.
Regards
Henrik
Received on Friday, 14 May 2010 09:53:07 UTC