Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: redirect to webpage
Date: Wed, 31 Oct 2007 11:37:52 -0500	[thread overview]
Message-ID: <4728AF60.4090102@riverviewtech.net> (raw)
In-Reply-To: <20071031111119.hc54s7z4e80sc0ws@webmail.harrisonburg.k12.va.us>

On 10/31/07 10:11, dhottinger@harrisonburg.k12.va.us wrote:
> Not sure if this is the best practice, but it works fine.  What I would 
> like to do, instead of dropping this traffic is have it sent to an 
> internal webserver that has our acceptable use policy on it.  Is there a 
> REDIRECT command, or what would be the best way to accomplish this.  
> Most of this traffic is actually on port 443, and I cant funnel this 
> through my transparent proxy (squid).

Yes.  You want to look in to DNATing the traffic to an internal web 
server that is specifically set up to do what you are wanting to do.

Hint, set up the web server of your choice that will answer any and all 
domain names with one single page, the 404 (not found) error page that 
is the content that you want displayed.  That way no matter what is 
requested, your page will be displayed.  I would also suggest that you 
include the headers to control how long the page is cached for, say 5 - 
15 minutes.  You may or may not want to return a 200 reply code.  Some 
browsers will display ""Friendly 404 pages and thus not display your text.



Grant. . . .

  reply	other threads:[~2007-10-31 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 15:11 redirect to webpage dhottinger
2007-10-31 16:37 ` Grant Taylor [this message]
2007-10-31 17:02   ` dhottinger
2007-10-31 18:34     ` Grant Taylor
2007-11-01  0:57       ` dhottinger
2007-11-01  9:21         ` G.W. Haywood
2007-11-01  9:56         ` Pascal Hambourg
2007-11-01 16:19         ` Grant Taylor

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=4728AF60.4090102@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox