Using a wildcard for the IP address is perfectly fine. The problem is as you
point out, the fact that the first virtual host is not the named one, and since
it is the first, all requests will be processed according to the rules within
that.
-ascs
From: Victor
I will be out of the office April 17-21. I will return to the office on 4/24. I
will be checking email periodically, but if you need immediate assistance,
please call Rogelio at 244-2326 or Jo Ana at 244-2153.
Cheryl
-
The off
We are encountering a problem with IE 6.0 SP1 where it seems to have
problems with compressed data being served from the IBM HTTP Server
2.0.47 (Apache). Using the mod_deflate option to compress static and
dynamic data on the run.
The problem is that the client side will "hang" and do nothing,
Hi,
I am using apache 2.2 on windows 2k3. I stop and start the service using the
windows apache monitor utility. I have noticed that every time I stop the
apache service, all the rotatelog.exe 's are orphaned. In just a couple of
restarts, I could have 50 or more orphaned. they do not exit
Yes, that should work. But if you're using name-based virtual hosting, it would be best to put an actual IP in there () rather than wildcards.Cheers,Victor
On 4/13/06, Stuart, Ed <[EMAIL PROTECTED]> wrote:
>> If I'm reading this right, you could change to and then have two >>>separate Virtu
I'm trying to get a config worked out using VirtualDocumentRoot and for
the life of me can't remember what I did to get this working on a
previous server. My basic setup is as follows:
VirtualDocumentRoot /usr/local/apache/sites/%-2.0.%-1/%-3+/htdocs
VirtualScriptAlias /usr/local/apache/sites
and most http/s proxies would block outbound ssl connections to ports other
than 443. so if you ran your public secure webserver on a port other than
443 most people wouldnt be able to access it, unless u do the port
forwarding mapping suggested by Kishore, which is the same thing anyway.
The first thing is there is no obvious advantage of using a different port for SSL, usually people tend to run standard services on non-standard ports mainly to decieve/hide your Services (SSH, etc) from external network scans.
As an example some people tend to run their SSH on a different port
Gary,
In general, the client, normally a web browser, knows that https is done over port 443. So most browsers will go to port
443 automatically when the URL begins with https. There is really no way to 'trick' the browser from the server-side. I
assume that the idea of moving the HTTPS listener
>
> If I'm reading this right, you could change to
and then have two >>>separate VirtualHost containers
, one listening for http and one for https (second one being
), >ith the exact same Redirect. Using mod_rewrite
may be a more elegant solution, though.
> -Victor
On 4/13/06, Schultz, Gary - COMM <[EMAIL PROTECTED]> wrote:
>
> I'm testing SSL (mod_ssl) on Apache 2.0.55 Win32. Some consultants that
> conducted a security analysis suggested using ports other than the default
> 443 port for SSL. Is it possible to configure Apache to use a port other
> than 443
> CustomLog "|/bin/sed 's/;variable/?variable' | /usr/sbin/rotatelogs
> /etc/httpd/logs/mysite.%Y-%m-%d-%H_%M_%S 5M" combined
- Instead of writing to a sed pipe, parsing the logfile before sending it
to Livestats is much better IMO.
- Does this command run fine from the command line? I.e. does 'ec
Suggest you get new consultants. ;)On 4/13/06, Schultz, Gary - COMM <[EMAIL PROTECTED]
> wrote:
I'm testing SSL
(mod_ssl) on Apache 2.0.55 Win32. Some consultants that conducted a
security analysis suggested using ports other than the default 443 port for SSL.
Is it possible to configure
I'm testing SSL
(mod_ssl) on Apache 2.0.55 Win32. Some consultants that conducted a
security analysis suggested using ports other than the default 443 port for SSL.
Is it possible to configure Apache to use a port other than 443 for SSL and have
the URL stay the same, that is, be able to use
If I'm reading this right, you could change to and then have two separate VirtualHost containers , one listening for http and one for https (second one being ), with the exact same Redirect. Using mod_rewrite may be a more elegant solution, though.
-VictorOn 4/12/06, Stuart, Ed <[EMAIL PROTECTED
For name based hosting you have to define at least one IP and port using NameVirtualHost. So change NameVirtualHost *:80 to NameVirtualHost IP:80 and then you have to use for every VirtualHost container. Otherwise the or will result in the first Virtual Host to be served by Apache. So what yo
The following may qualify as a minimum configuration... Have not tested it,
though. I assumed you were using worker MPM.
In the config below, I believe the virtual host can explain
your problem. See it has DocumentRoot /var/www/html ??? I believe you meant
this virtual host directive to read
You would not by any chance have the directive
KeepAlive Off
in your configuration ?
-ascs
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 12, 2006 12:05 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] HTTP response Header from Apac
Don't know if you tried this or not but did you clear your browser
cache, maybe its just loading a cached copy.
Mark Van Crombrugge wrote:
Here is my HTTPD.CONF file, the VirtualHost is at the bottom.
(www.testsite.org)
I have compared it to a httpd.conf file on another server that runs fine a
>
>
> Here is my HTTPD.CONF file, the VirtualHost is at the bottom.
> (www.testsite.org)
>
> I have compared it to a httpd.conf file on another server that runs fine and
> neither me nor my colleague can see any differences...
Well, I don't see anything wrong with it offhand, although I am not
This is not a _minimal_ configuration.
-ascs
-Original Message-
From: Mark Van Crombrugge [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 13, 2006 4:25 PM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Documentroot does not redirect...
Here is my HTTPD.CONF file, the Virtua
Here is my HTTPD.CONF file, the VirtualHost is at the bottom.
(www.testsite.org)
I have compared it to a httpd.conf file on another server that runs fine and
neither me nor my colleague can see any differences...
Thanks in advance for your assistance.
Mark
-
### Section
In the HTTPD.conf, the directive 'DocumentRoot' is with the right uppercases
(allthough this seems to make no difference), I just type to fast in the
e-mail message.
-Original Message-
From: Boyle Owen [mailto:[EMAIL PROTECTED]
Sent: donderdag 13 april 2006 13:09
To: users@httpd.apache.or
Boyle Owen wrote:
From: Mark Van Crombrugge [mailto:[EMAIL PROTECTED]
Documentroot /var/www/html/website
First, spell the directive correctly... ie, "DocumentRoot".
FWIW - the directive itself is case-insensitive, as are -most- arguments
other than path/resource names.
-
Hi all.
I have an issue
which, I am sure someone out there has encountered in the past.
I have a website,
whose authors have written some of the URLs in a format which contains
characters which are not well liked by my log analysis tools (Deepmetrix
Livestats).
I would like to
> -Original Message-
> From: Mark Van Crombrugge [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 13. April 2006 12:20
> To: users@httpd.apache.org
> Subject: [EMAIL PROTECTED] Documentroot does not redirect...
>
> When I put the file "index.htm" in my DocumentRoot
> (/var/www/html) it disp
I made some tests just to confirm what I already knew, but was not able to
reproduce the behaviour you describe.
Could you manage to reproduce the problem with a minimal configuration (one or
two VH only and just the strict minimum set of directives) and post it ?
-ascs
_
When I put the
file "index.htm" in my DocumentRoot (/var/www/html) it displays in my
browser.
When I put that file
in "/var/www/html/website" and add the following to
httpd.conf:
NameVirtualHost
*:80
Documentroot
/var/www/html/website
ServerName www.website.org
When I enter www.webs
28 matches
Mail list logo
