So from what I'm gathering, if I have several virtual hosts defined in my
httpd.conf file (Using Include) then in order to secure them via SSL, each one
would have to have it's own IP address? So for example, each of these virtual
host containers in each .conf file included begins with:
In my main httpd.conf file, I have numerous include files which include
virtual hosts like so:
Include /usr/local/apache/conf/conf.d/devl00.conf
Include /usr/local/apache/conf/conf.d/devl01.conf
Include /usr/local/apache/conf/conf.d/devl02.conf
So if I access http://devl02.mydomain.com/ then I
Are these IP-based virtual hosts or name-based virtual hosts? See
http://httpd.apache.org/docs/2.0/vhosts/name-based.html
--Cliff
On 10/15/07, Bernard Barton [EMAIL PROTECTED] wrote:
In my main httpd.conf file, I have numerous include files which include
virtual hosts like so:
Include
These are name based virtual hosts. Numerous hosts, only one IP
address. So each of the included .conf files below such as devl00.conf
and devl01.conf begin with something like this:
VirtualHost 172.35.241.47
ServerName devl02.mydomain.net
ServerAdmin [EMAIL PROTECTED]
LogLevel
If all you want to do is redirect / on your non-SSL Port to / on
your SSL port, you could use a zero second redirect.
e.g. put this in your index.html for the port 80 virtual host:
meta http-equiv=refresh content=0;url=https://devl02.mydomain.com/; /
And have your real content in a different
Thanks, but I'm trying to get through this without any code changes.
It's ALMOST working! But no cigar.
Brian Hayward wrote:
If all you want to do is redirect / on your non-SSL Port to / on
your SSL port, you could use a zero second redirect.
e.g. put this in your index.html for the port
Mads Toftum wrote:
This will never happen because you're already inside the Port 443
vhost container.
Stupid oversight on my behalf. Thanks to those that pointed this out.
NameVirtualHost 10.0.0.2:80
VirtualHost 10.0.0.2:80
ServerName www.sancho2k.net
Redirect /
On Fri, Jan 17, 2003 at 09:39:12PM -0700, Sancho2k.net Lists wrote:
NameVirtualHost 10.0.0.40:443
VirtualHost 10.0.0.40:443
[SNIP]
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
This will never happen because you're already inside the Port 443
vhost
Greetz all,
I'm trying to force one of my virtual hosts to use https when http is
requested by a mod_rewrite rule. I am testing the implementation using
curl.
When I specify https in my url, curl will grab the correct page:
[root@molodetz:~]# curl https://family.sancho2k.net
!DOCTYPE HTML
- What is actually being server for that address ???
It is probably your default page you have put there..
Rgds
Jeff
- Original Message -
From: Sancho2k.net Lists [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, January 18, 2003 2:39 PM
Subject: HTTP -- HTTPS rewrite not working
Title: http + https
Im trying to configure my server to use SSL just for requests to a specific directory.
Ive read the manuals, installed mod_ssl + certificate and all seemed to be working fine,
HTTP access to the server at large goes ahead and http accesses to the secured directory
I have configured my httpd.conf ssl.conf file also but probably I am not
doing some thing right as my site is not opening as required.
My Q is
How do i configure my http.conf ssl.conf in apache 2.0
if -
I have one page which has to be http
I have the second page which has to be https with
[EMAIL PROTECTED] wrote:
RedirectMatch (.*) https://d.com$1
Won't this create an infinate loop?
I could be wrong, but I think RedirectMatch will pick up the hit via http or https,
and attempt to send the user to https://d.com$1 even if the user came via https in
the first place.
It
In article [EMAIL PROTECTED] you wrote:
Quoting Owen Boyle [EMAIL PROTECTED]:
If you want to be more specific so that
http://d.com/foo/bar.html -- https://d.com/foo/bar.html
then use something like:
RedirectMatch (.*) https://d.com$1
Won't this create an infinate loop?
I could
Quoting Owen Boyle [EMAIL PROTECTED]:
If you want to be more specific so that
http://d.com/foo/bar.html -- https://d.com/foo/bar.html
then use something like:
RedirectMatch (.*) https://d.com$1
Won't this create an infinate loop?
I could be wrong, but I think RedirectMatch will pick
Farooq Khan writes:
I have installed apache with mod_ssl. Briefly, I want all http requests to a
particular
VirtualHost to be redirected to https for the same VirtualHost. Do I use
mod_rewrite to do
this?
I have set up 4 VirtualHosts in the order:
VirtualHost a.com:80
Hi,
This is my first post to the list. I've setup 2 Apache + mod_ssl listeners on
the same machine for our test and development environments. The test listener
is on the standard ports. The development listener is listening on for
HTTP and for HTTPS. This works only if my URL looks
Hi,
Simply it's not possible !
Regards
Rajidhar E
- Original Message -
From: Michael Champagne [EMAIL PROTECTED]
Date: Thursday, September 27, 2001 2:30 pm
Subject: HTTP/HTTPS both on non-standard ports?
Hi,
This is my first post to the list. I've setup 2 Apache + mod_ssl
But this will only work, if you have one VirtualHost!
GreetingX,
Alex
--- Charles Kathryn Brown [EMAIL PROTECTED] schrieb:
From the httpd.conf file:
### Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
#
From the httpd.conf file:
### Section 2: 'Main'
server configuration # #
The directives in this section set up the values used by the
'main' # server, which responds to any requests that
aren't handled by a # VirtualHost
definition. These values also provide defaults
for # any
--- Thomas Binder [EMAIL PROTECTED] schrieb:
Hi!
On Thu, Aug 16, 2001 at 02:15:09PM +0200, Owen Boyle wrote:
[Both hosts with the same content]
The only simple way is with two VHs with the same DocumentRoot - even
though it violates the Prime Directive (which is: Never Define
On Thu, Aug 16, 2001 at 03:09:34PM +0200, Thomas Binder wrote:
Hi!
On Thu, Aug 16, 2001 at 02:15:09PM +0200, Owen Boyle wrote:
I'd suggest using a reverse proxy for that, i.e. let the SSL VHost be
just a reverse proxy for the normal server.
That is more or less what I've done a couple
Hi!
On Fri, Aug 17, 2001 at 11:39:20AM +0200, Alex Pircher wrote:
I'd suggest using a reverse proxy for that, i.e. let the SSL VHost be
just a reverse proxy for the normal server.
An interesting idea, but this would of course require the additional
module mod_proxy.
Sure, but if Apache
Proxies, Intranets, mod_rewrite...
Aren't we getting a little carried away? All the guy was trying to do
was have two VHs running off the same DocumentRoot. Now we all know you
can do this with two DocumentRoot directives pointing to the same
directory but that violates the Prime Directive
On Fri, Aug 17, 2001 at 12:36:55PM +0200, Owen Boyle wrote:
Proxies, Intranets, mod_rewrite...
Aren't we getting a little carried away?
That's more or less because this thread has evolved to answering other peoples
problems too.
All the guy was trying to do
was have two VHs running off
Hi,
Are you saying go http://www.blah.com -- https://www.blah.com ? If so, just
use a redirect in the first VirtualHost1.2.3.4
ServerName www.blah.com
Redirect / https://www.blah.com
/VirtualHost
Lanny Baron wrote:
Hi,
Are you saying go http://www.blah.com -- https://www.blah.com ? If so, just
use a redirect in the first VirtualHost1.2.3.4
ServerName www.blah.com
Redirect / https://www.blah.com
...
All the guy was trying to do
was have two VHs running off the same DocumentRoot. Now we all know you
can do this with two DocumentRoot directives pointing to the same
directory but that violates the Prime Directive (which is: Never Define
Anything Twice).
As long as we're
Hi Owen,
Then what's the biggy to just do 2 vhosts?? One regular and one https.
--Lanny
Owen Boyle writes:
Lanny Baron wrote:
Hi,
Are you saying go http://www.blah.com -- https://www.blah.com ? If so, just
use a redirect in the first VirtualHost1.2.3.4
Lanny Baron wrote:
Then what's the biggy to just do 2 vhosts?? One regular and one https.
For then, one would violate the Prime Directive and have to Define the
Same Thing Twice and thou should not goest that way for it is a way of
pain and much suffering and leads inevitably to you changing
-Original Message-
From: Owen Boyle [mailto:[EMAIL PROTECTED]]
Sent: 17 August 2001 15:19
To: [EMAIL PROTECTED]
Subject: Re: Serving HTTP HTTPS in one VHost-Config?
Lanny Baron wrote:
Then what's the biggy to just do 2 vhosts?? One regular and
one https.
For then, one would violate
On Fri, 17 Aug 2001, Owen Boyle wrote:
Lanny Baron wrote:
Then what's the biggy to just do 2 vhosts?? One regular and one https.
For then, one would violate the Prime Directive and have to Define the
Same Thing Twice and thou should not goest that way for it is a way of
pain and much
Well what I have done for things like my mail toaster which gives users web
based email like microshaft or yahoo, enabled with SSL i have a vhost with a
regular http that has the redirect to another site on the same server.
webmail.blah.com -- secure.blah.com/cgi-bin/path_to_executable
So I
Is it possible to serve HTTP HTTPS within one Virtual Host-
Configuration?
NameVirtualHost 123.123.123.123:80
NameVirtualHost 123.123.123.123:443
VirtualHost www.domain.com:80 www.domain.com:443
ServerName www.domain.com
SSLEngine on
SSLCertificateFile /.../server.crt
SSLCertificateKeyFile
Alex Pircher wrote:
Is it possible to serve HTTP HTTPS within one Virtual Host-
Configuration?
NameVirtualHost 123.123.123.123:80
NameVirtualHost 123.123.123.123:443
VirtualHost www.domain.com:80 www.domain.com:443
ServerName www.domain.com
SSLEngine on
SSLCertificateFile
Is it possible to serve HTTP HTTPS within one Virtual Host-
Configuration?
NameVirtualHost 123.123.123.123:80
NameVirtualHost 123.123.123.123:443
VirtualHost www.domain.com:80 www.domain.com:443
ServerName www.domain.com
SSLEngine on
SSLCertificateFile /.../server.crt
Alex Pircher wrote:
Is it possible to serve HTTP HTTPS within one Virtual Host-
Configuration?
NameVirtualHost 123.123.123.123:80
NameVirtualHost 123.123.123.123:443
VirtualHost www.domain.com:80 www.domain.com:443
ServerName www.domain.com
SSLEngine
Alex Pircher wrote:
OK. So only NameVirtualhost 123.123.123.123
You'll still get a warning with this. To be absolutely safe, use:
NameVirtualhost 123.123.123.123:80
Then you can have as many NBVHs as you like on port 80 and exactly one
SSL VH on port 443.
What's the real problem? Do you
for the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED]
-Original Message-
From: Owen Boyle [mailto:[EMAIL PROTECTED]]
Sent: 16 August 2001 13:15
To: [EMAIL PROTECTED]
Subject: Re: Serving HTTP HTTPS in one VHost-Config?
Alex Pircher
the Rewrite-Engine - that means SSL comes before Rewrite.
You should think about a new Configuration-Directive:
HTTPandHTTPS [httpport [httpsport]] - Serving HTTP HTTPS in one VHost-Config
I thought that serving HTTP and HTTPS in one VHost-Config is rather general
On Thu, Aug 16, 2001 at 01:48:33PM +0100, [EMAIL PROTECTED] wrote:
One of Ralf's slides from ApacheCon 2000 has a rewrite rule to do this. I've
wanted to implement it for some time, but I couldn't figure it out!
http://www.modssl.org/docs/apachecon2000/slide-020-n.html
What exactly is it
--- Mads Toftum [EMAIL PROTECTED] schrieb:
On Thu, Aug 16, 2001 at 01:48:33PM +0100, [EMAIL PROTECTED] wrote:
One of Ralf's slides from ApacheCon 2000 has a rewrite rule to do this. I've
wanted to implement it for some time, but I couldn't figure it out!
=RIGHT/A
(actually, that's not a good example of what I was trying to illustrate...
But hopefully you get the picture...)
- Original Message -
From: Owen Boyle [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 16, 2001 2:54 AM
Subject: Re: Serving HTTP HTTPS in one VHost
hi
is it possible to configure apache such as: if the
client has a certificate enter page X and if client
has no certificate enter page Y??
Miguel FOntes
-
Email Enviado utilizando o serviço MegaMail
What's the standard way (accross all SSL vendors) to find out in a apache
module
if you are in a http/https mode?
I was assuming "request_rec-parsed_uri.scheme" to return me http/https, but
it returns NULL!
Also looks like ap_table_get(r-subprocess_env,"HTTPS") is not
ore detail on exactly what you're trying
to do and in what way it's failing, someone on this list will be able to
help.
Deb
-Original Message-
From: Moss, Peter [mailto:[EMAIL PROTECTED]]
Sent: October 16, 2000 3:22 PM
To: '[EMAIL PROTECTED]'
Subject: HTTP/HTTPS and HTTP Proxy
All,
Deborah, all,
I've setup HTTP/HTTPS 2.7.1-1.3.14 mod-ssl.
HTTP and HTTPS services work!
The proxy does not work.
I'm using the same proxy directives as I used in my 1.3.12 proxy
installation, ProxyPass, ProxyPassReverse directives etc.
I think proxy is an optional module so I had to change
it was as simple as adding "--enable-module=proxy" on line 674
of /mod_ssl../configure script
HTTP, HTTPS and proxy to HTTP sites works like a charm.
Anyone knows (done) conversion of IIS/COM objects to apache modules ? I
think I'm going to try mod_plsql? I saw on modules.
All,
My setup is:
apache 1.3.14
openssl 0.9.6
mod-ssl 2.7.1
FreeBSD 4.0
Rebuilt/Installed it today, not problems so far. (Test CERT) SSL works
in IE and NS
Question:
===
I want to configure Apache as HTTPS -- HTTP proxy, basically
I want to "hide" a couple of application servers behind
On Wed, May 17, 2000 at 03:20:15PM -0600, Diana Shepard wrote:
Can I use one apache with mod_ssl config file to
service both https and http? My install of apache
with SSL is working fine, but my web application
executes a java servlet which POSTs to an http CGI.
apache chokes when it hits
Hi.
I'm having some trouble setting up both HTTP and HTTPS on the same server (I
want to run both through the same Apache using Apaches virtual hosting).
Could somebody please help me out on this?
I seem to only get one of these working. Either it's HTTPS or HTTP, but
never both of them.
Nevermind my last mail.
I had forgotten to specify which ports it will listen to with the "Listen"
directive in httpd.conf.
Thanks for baring with me anyway.
Regards,
Kenneth Mutka
__
Apache Interface to OpenSSL (mod_ssl)
"it's usually most simples to run a single instance where you enable SSL
only for those virtual hosts that need it. "
But it does not talk about making all this for only the main server.
at the end of the config, just use two virtual host sections, one on port
80 without SSL, one on port
Hi!
I'm trying to make my server https enabled, but without removing the
http server. I don't want to start digging into virtual hosts. Is this
possible?
I read the FAQ, and it mentions that:
"it's usually most simples to run a single instance where you enable SSL
only for those virtual hosts
:04 -0400 (EDT)
Subject: Making a http/https server
Hi!
I'm trying to make my server https enabled, but without removing the
http server. I don't want to start digging into virtual hosts. Is this
possible?
I read the FAQ, and it mentions that:
"it's usually most simples to run a single ins
55 matches
Mail list logo
