Re: HTTP Input header filter

2003-02-06 Thread Justin Erenkrantz
--On Thursday, February 6, 2003 9:07 AM -0500 Bill Stoddard <[EMAIL PROTECTED]> wrote: ap_http_filter logic in the header parser filter, create a new API to push bytes back to the core_input_filter when the header parser filter reads too many bytes and variations. Eww. Regardless, I'll wait to

Re: HTTP Input header filter

2003-02-06 Thread Bill Stoddard
Justin Erenkrantz wrote: --On Wednesday, February 5, 2003 4:32 PM -0500 Bill Stoddard <[EMAIL PROTECTED]> wrote: 1. Installing this filter for the duration of a connection. It is still a protocol filter, but it lasts for the duration of the connection. In order to handle pipelined connections, a

Re: HTTP Input header filter

2003-02-05 Thread Justin Erenkrantz
--On Wednesday, February 5, 2003 4:32 PM -0500 Bill Stoddard <[EMAIL PROTECTED]> wrote: 1. Installing this filter for the duration of a connection. It is still a protocol filter, but it lasts for the duration of the connection. In order to handle pipelined connections, an Hmm. I'm wondering if

Re: HTTP Input header filter

2003-02-05 Thread Bill Stoddard
Bill Stoddard wrote: Brian Pane wrote: Bill Stoddard wrote: Just a heads up in case anyone else is interested or is comtemplating working on this... I am rewriting much of the code called by ap_read_request to handle HTTP headers. Much of the function in rgetline_core, read_request_headers a

Re: HTTP Input header filter

2003-01-07 Thread Brian Pane
Joe Schaefer wrote: Greg Ames <[EMAIL PROTECTED]> writes: Joe Schaefer wrote: [...] Just looking over the 2.0 source, it looks to me like r->headers_in is an empty apr_table prior to the apr_table_overlap() call at the end of get_mime_headers_core(). I'll take your word f

Re: HTTP Input header filter

2003-01-07 Thread Joe Schaefer
Greg Ames <[EMAIL PROTECTED]> writes: > Joe Schaefer wrote: [...] > > Just looking over the 2.0 > > source, it looks to me like r->headers_in is an empty > > apr_table prior to the apr_table_overlap() call at the > > end of get_mime_headers_core(). > > > > I'll take your word for it. Pleas

Re: HTTP Input header filter

2003-01-07 Thread Greg Ames
Joe Schaefer wrote: Can r->headers_in ever contain any entries prior to the get_mime_headers_core() call? no (barring weird bugs of course). Just looking over the 2.0 source, it looks to me like r->headers_in is an empty apr_table prior to the apr_table_overlap() call at the end of get_m

Re: HTTP Input header filter

2003-01-07 Thread Joe Schaefer
"Bill Stoddard" <[EMAIL PROTECTED]> writes: > I am rewriting much of the code called by ap_read_request > to handle HTTP headers. Much of the function in rgetline_core, > read_request_headers and get_mime_headers_core is being > reimplemented in ap_http_headers_input_filter. Can r->headers_in

Re: HTTP Input header filter

2003-01-06 Thread Brian Pane
Bill Stoddard wrote: Just a heads up in case anyone else is interested or is comtemplating working on this... I am rewriting much of the code called by ap_read_request to handle HTTP headers. Much of the function in rgetline_core, read_request_headers and get_mime_headers_core is being reimpleme

HTTP Input header filter

2003-01-06 Thread Bill Stoddard
Just a heads up in case anyone else is interested or is comtemplating working on this... I am rewriting much of the code called by ap_read_request to handle HTTP headers. Much of the function in rgetline_core, read_request_headers and get_mime_headers_core is being reimplemented in ap_http_headers