Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Chip Upsal <Chip@CyberWolf.com>
To: Andrea Rossato <mailing_list@istitutocolli.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Update httpd.conf file:  Apache virtualhost not working behin d firewall.
Date: Sun, 22 Dec 2002 10:06:56 -0700	[thread overview]
Message-ID: <3E05F130.7000909@CyberWolf.com> (raw)
In-Reply-To: <3E043E98.2050509@istitutocolli.org>

I tend to agree...but i have tried all the documented and undocumented 
VirutalHost setups i could find. Furthermore, it is bothersome that the 
VirtualHost work fine when the HTTP server is not behind the IPTables 
firewall.

Andrea Rossato wrote:

> Chip Upsal wrote:
>
>> I doubt it is strictly an apache problem as if we remove the firewall 
>> and
>> assign the external ip address to the server it all works well.
>
>
> if you solved the iptables problem and you are properly forwarding 
> traffic to the internal box, that's probably an apache issue: as far 
> as i understand you are creating a name based virtul host: apache 
> should look in the _http_headers_ to respond with the correct web 
> server name. (http headers are indeed in packet payloads and iptables 
> will not touch them when S/DNATting).
>
> so:
>
> NameVirtualHost 192.168.0.2
> <VirtualHost 192.168.0.2>
>    ServerName site4.company.com
>    ServerAlias site4*
>    ServerAdmin admin@company.com
>    DocumentRoot D:/web_root/foo4
>    ErrorLog logs/site4.cyberwolf.com-error_log
>    CustomLog logs/site4.cyberwolf.com-access_log common
> </VirtualHost>
>
> hope that this is going to work (is working for me, though).
> andrea
>



      reply	other threads:[~2002-12-22 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 21:36 Update httpd.conf file: Apache virtualhost not working behin d firewall Chip Upsal
2002-12-21 10:12 ` Andrea Rossato
2002-12-22 17:06   ` Chip Upsal [this message]

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=3E05F130.7000909@CyberWolf.com \
    --to=chip@cyberwolf.com \
    --cc=mailing_list@istitutocolli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox