FWIW, twitter.com runs custom (non-apache code) that does the following: We send a 417 to any HTTP/1.0 request with a Expect header. We send a 417 to any HTTP/1.1 request with a Expect header that is not case-insensitive 100-continue (this includes empty Expect headers but we do allow some ridiculousness like Expect: , , 100-continue) We then remove the Expect header for further processing, responding with 100 Continue if necessary. On Thu, Sep 12, 2013 at 5:51 PM, Mark Nottingham <mnot@mnot.net> wrote: > > On 13/09/2013, at 7:03 AM, Roy T. Fielding <fielding@gbiv.com> wrote: > > > My preferred solution is to remove the garbage, define > > 100-continue, allow it to be processed by intermediaries, > > and leave a Note behind to explain the failed extension > > mechanism and usage of 417. > > +1 > > > -- > Mark Nottingham http://www.mnot.net/ > > > > >
Received on Friday, 13 September 2013 15:42:17 UTC