Have you considered the use of mod_rewrite instead ???
On Friday 15 February 2013 16:01:25 Alejandro Casagrande wrote:
> Yes, Reindl. Thank you for your concerns. The first thing that I did when I
> realize this problem was to stop apache and set the firewall to block port
> 80, in order to stop the traffic.
> In testing using apache in another port. I'm managed to block proxy
> requests, but I want that this requests consume the lower traffic possible,
> so that is why i was asking if instead apache responding 404 or 403, closes
> the connection so no outgoing traffic is made.
> Proxy is enabled only for a virtual host with a specific domain.
> I really appreciate your suggestions, thank you again.
> Best regards
> 2013/2/15 Reindl Harald <email@example.com>
> > have you set
> > <IfModule mod_proxy.c>
> > ProxyRequests Off
> > </IfModule>
> > a i suggested hours ago?
> > it does not need to be enabled, even for common proxy-setups in apache
> > and it SHOULD NOT be enabled except with specific needs in a
> > <Location> or <Vhost>
> > Am 16.02.2013 00:37, schrieb Alejandro Casagrande:
> > > Thank you for your suggestions Steven. Unfortunately i need mod_proxy
> > because i need to redirect requests to
> > > another web server in another port.
> > >
> > > Besides disabling mod_proxy, I would like that apache does not respond
> > to this requests as they will generate
> > > traffic responding 404.
> > >
> > > 2013/2/15 Steven Kucharzyk <firstname.lastname@example.org <mailto:
> > email@example.com>>
> > >
> > > __
> > >
> > >
> > > I would like to suggest ... starting with Apache itself and unload,
> > remove, disable any mod_proxy modules and
> > > directives ... it does no good to establish mod_security rules to
> > block a service that you don't want running
> > > or understand how to control. I would do that with all modules you
> > don't understand and "park" or eliminate all
> > > virtual_host configurations that you yourself have not set up and
> > understand completely
> > ------------------------------------------------------------------------------
> > The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
> > is your hub for all things parallel software development, from weekly
> > thought
> > leadership blogs to news, videos, case studies, tutorials, tech docs,
> > whitepapers, evaluation guides, and opinion stories. Check out the most
> > recent posts - join the conversation now.
> > http://goparallel.sourceforge.net/
> > _______________________________________________
> > mod-security-users mailing list
> > firstname.lastname@example.org
> > https://lists.sourceforge.net/lists/listinfo/mod-security-users
> > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs:
> > http://www.modsecurity.org/projects/commercial/rules/
> > http://www.modsecurity.org/projects/commercial/support/
Mail delivery confirmation requests:
Confirmation requests, are sent to verify delivery by the mail delivery system and does not imply, the message was actually read/ understood by the intended recipient(s)
Indiscriminate confirmations to unknown parties may jeopardize your privacy.
This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. The information contained in this email may be subject to the export control laws and regulations of the united states, potentially including but not limited to the export administration regulations (ear) and sanctions regulations issued by the u.s. Department of treasury, office of foreign asset controls (ofac). As a recipient of this information you are obligated to comply with all applicable u.s. Export laws and regulations.