From: Rayed Alrashed <rayed@saudi.net.sa>
To: Alex <alex@hackgod.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Forking inside netfilter queue
Date: Thu, 03 May 2007 22:20:55 +0300 [thread overview]
Message-ID: <463A3617.7050702@saudi.net.sa> (raw)
In-Reply-To: <002901c78d97$4f60f1c0$0a00080a@rhea>
> Unless there are a real lot of these addresses that are permitted, and
> they change rapidly, then I'd expect it would be a better design to
> get all the valid URIs from the MySQL query on init and store them in
> a linked list.
I am afraid this not an option, because my final goal is to integrate my
application with external vendor database using the vendor own API.
> Also, people already do this type of thing with an HTTP proxy like
> squid before the HTTPd.
I've tested HTTP proxy before, but the overhead is very big, and I
couldn't get the proxy to handle high loads.
Another problem with proxy servers is using the proxy own IP for
outgoing request, unfortunately using the same IP for many requests
trigger many IDSes to block the proxy IP.
What I am trying to do is a light weight HTTP filter, by searching for
HTTP requests in packet traveling on the wire, with minimal TCP
reassembly to find HTTP requests spanning more than one packet.
next prev parent reply other threads:[~2007-05-03 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 13:18 Forking inside netfilter queue Rayed
2007-04-30 13:47 ` Jan Engelhardt
2007-05-01 6:30 ` Rayed
2007-05-01 8:32 ` Jan Engelhardt
2007-05-01 18:27 ` Can't get --dport to work Joel Lindsay
2007-05-01 20:28 ` Krishnamoorthy (Siva) Sivakumar
2007-05-03 15:25 ` Forking inside netfilter queue Alex
2007-05-03 19:20 ` Rayed Alrashed [this message]
2007-05-03 17:48 ` Alex
2007-05-03 18:39 ` Rayed Alrashed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463A3617.7050702@saudi.net.sa \
--to=rayed@saudi.net.sa \
--cc=alex@hackgod.org \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.