So, if I added this as a filter, I still *could* use it with proxy,
right?
I did it in the CONNECT part because wanted a generalized byte tunnel
that would throttle down connection speeds for any protocol, HTTP +
SSL usually, but also it could be used for telnet, ssh, whatever. I
also have a dedicated program to do this, but being able to configure
the security (connect) proxy makes the setup process transparent to
the user.
I'll look into filters, and see if I could get them to work with
CONNECT as well.
Thanks for the feedback.
-bill
From: Graham Leggett <[EMAIL PROTECTED]>
Date: Sat, 18 May 2002 11:53:52 +0200
Bill O'Donnell wrote:
> I have a patch which I created to simulate users on slow or asymmetric
> connections. This patch adds two configuration settings to change the
> speed of upload or download thru a tunnelling (CONNECT) proxy.
This is really useful functionality, however I don't think it's a good
idea to add it to proxy - as it means you can only use it with the
proxy.
A better idea would be to implement it as a filter, which will allow it
to be used anywhere in Apache. I do notice you implemented it in the
CONNECT part of the proxy - was there a reason for this? The CONNECT
part is one of the last bits that never used filters.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
