Re: Expect: non-100 messages

> See > (I'd propose to continue the conversation over there). Done. Thanks for initiating the discussion. > > The HTTP spec does specify that the hop-to-hop decision MUST be made > > at a protocol level > > (

Re: Expect: non-100 messages

s only injected by a proxy with a known next-hop 1.0 or lower server. Similar behavior with new Expect headers would be just fine in our case. Charles On Thu, Apr 3, 2008 at 1:54 PM, Julian Reschke <[EMAIL PROTECTED]> wrote: > Charles Fry wrote: > > > Greetings Apache Developers, >

Expect: non-100 messages

Greetings Apache Developers, We have implemented an Apache module which needs to process incoming Expect headers for non-100-expectations. The version of server/protocol.c currently in the trunk has a hard-coded Expect header check that handles "Expect: 100-continue", but fails on any other expect

Re: ap_setup_client_block and Content-Length

Right, but then I have to parse it myself, and basically repeat all of the work of ap_setup_client_block, which I would have preferred to avoid... Charles On Fri, Feb 15, 2008 at 11:25 AM, Nick Kew <[EMAIL PROTECTED]> wrote: > On Fri, 15 Feb 2008 11:18:47 -0500 > "Charles Fry&q

Re: sending provisional response codes from a filter

All right. I finally resolved this, and it ends up the code works just fine, it's just that the input filter wasn't set properly, but I didn't notice due to the spurious 103 I was observing due to my modification of http_protocol. Whew. Charles On Feb 7, 2008 5:17 PM, Char

Re: sending provisional response codes from a filter

ap_pass_brigade(f->c->output_filters, bb); Does something else need to be done/happening to allow me to send a provisional response? This doesn't seem to work using ap_get_status_line(100) instead of "103 Checkpoint" either. Any thoughts or pointers would be appr