o (Alexander Farber) o (Marc Lehmann, Kees Vonk) o (Ime Smits) o (Michele Beltrame) o (Surat Singh Bhati, Paul Cotter ) o (Aaron Johnson, Cliff Rayman, Yann Kerhervé) o (Daniel Bohling) o (Kevin Swope, Jamie) o corrected the math example with 56k modem, where the result was times and not seconds (Thanks to the students from my class at YAPC:: Europe 2000) o corrected the math example using the Max Client formula (for split code sets) o verified that squid's default read-ahead (send) buffer is of 16KB o corrected another math example with calculating real Max Clients when shared memory is taken into an account (Thanks to an anonymous bearded student from from my class at YAPC:: Europe 2000) o new section: "Measuring the Memory of the Process" o The "Forking and Executing Subprocesses from mod_perl" sections has been almost completely rewritten o The "Global vs.
o bring the warnings section up to date with perl 5.6 (Rafael Garcia-Suarez) o cover the 5.6's CHECK block in addition to INIT (Rafael Garcia-Suarez) o adopt sections from the modperl faq and rewrite the whole security configuration section o extended on method handlers (Per Einar Ellefsen) o show an example on how to load the mod_perl related config only when mod_perl is loaded (Rafael Garcia-Suarez) o More information about Perl Set Env/Perl Pass Env/Perl Setup Env w/ practical example [Per Einar] o Extend on Perl Set Var/Perl Add Var but more importantly, add information about subrequests w/ lookup_file and dir_config provided by Matt Sergeant in this thread: [Per Einar] o add more benchmarking tools refs: HTTP:: Web Test, HTTP:: Monkeywrench, HTTP:: Test Engine, HTTPD:: Bench:: Apache Bench o update the benchmark in the section "Apache::args vs. o added a new section: "Potential Drawbacks of Memory Sharing Restriction" o most of the internal links were changed to use the whole title and not only first few words. o The documents themselves are now referenced as guide::something, e.g.
Though as of this writing in Apache 2.0 it doesn't really do what it did in Apache 1.3. The issue is that buckets from one request may get buffered and not sent during the lifetime of the request, so it's not easy to give a truly accurate count of "bytes sent to the network for this response".
Usually you will set this value indirectly by returning the status code as the handler's function result.
The proxy handler needs to send to the client, whatever status code the proxied server has returned, while returning we have mentioned that sometimes a handler runs to a successful completion, but may need to return a different code, which is the case with the proxy server.
Assuming that the proxy handler forwards to the client whatever response the proxied server has sent, it'll usually use was used to implement the proxy.