HTTP_REFERER problem

[Daniel Stasinski]

I was able to block the links coming from a specific pedophile domain (I
redirect them to fbi.gov) but there are other instances where I want to
examine the google/bing/etc query strings to look for specific search terms
that could direct them to the correct resources or warn the channel ops
that the person is probably up to no good.


On Mon, Mar 9, 2015 at 12:44 AM, Ed <plug at 0x1b.com> wrote:

> Daniel,
>
> Do the blocking in the web server, not PHP. You want to push this kind
> of stuff as upstream in your system as you can get it - if you can
> block them at your firewall, even better.
> Look at the Access Control section, if you are using httpd 2.4:
> https://httpd.apache.org/docs/2.4/howto/access.html
>
> the section - Access control by arbitrary variables - looks to have
> what you want with HTTP_REFERER -  like so:
>
> <If "%{HTTP_REFERER} == 'Badland.org'">
>     Require All Denied
> </If>
>
> that's just some quick cut & paste, but a good example of what httpd
> 2.4 might look like - ymmv


-- 
| ---------------------------------------------------------------
| Daniel P. Stasinski
| daniel at GenericInbox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20150309/60e85781/attachment.html>