Joe Schaefer [EMAIL PROTECTED] writes:
Glenn Strauss [EMAIL PROTECTED] writes:
[...]
You suggested always using READBYTES. If a POST used chunked T-E to
send input, then when HTTP_IN is reading chunk trailers, too much data
might be read, i.e. the next request line might be read. What
probably obvious to those doing the load balancing work, but just in case...
url in this case is ip:port, which ap_proxy_get_balancer() doesn't handle
simple working testcase in case this helps testing
connect and send CONNECT 0.0.0.0:8080\r\n
get back:
: 48545450 2F312E30 20323030
Glenn Strauss [EMAIL PROTECTED] writes:
[...]
This just occurred to me: why not promote HTTP_IN to be a
connection level filter, and add a buffer brigade to http_ctx_t?
IIRC Bill Stoddard posted something like this about a year ago.
He and Brian Pane also discussed inverting the input
--On Friday, August 13, 2004 10:02 AM -0700 Mathihalli, Madhusudan
[EMAIL PROTECTED] wrote:
I was wondering if there's any potential harm in increasing the
LimitRequestFieldsize from it's current value of 8k to something more
(like 32k).
Instances that need to support larger header sizes
Grretings All,
Get the following while trying a build on a NetWare platform form CVS 2.1
HEAD:
Generating Release\proxyajp_cc.opt
Compiling proxy_ajp.c
Compiling proxy_util.c
Compiling c:\projects\gccnlm\ajplib/ajp_header.c
Compiling c:\projects\gccnlm\ajplib/ajp_msg.c
Compiling
