On Tue, Oct 27, 2009 at 11:15 AM, André Warnier wrote:
> Well, kind of, but one could argue about this. ;-)
> It seems to me that we are just at the grey line in-between here.
> Maybe I should have added one more HTTP VirtualHost in my example, just to
> settle it.
It doesn't harm to have this
Tom Evans wrote:
On Tue, 2009-10-27 at 07:28 +0100, André Warnier wrote:
Krist van Besien wrote:
On Mon, Oct 26, 2009 at 9:01 PM, André Warnier wrote:
The other way I could think of would be to use virtual hosts, like
Listen 80 HTTP
Listen 443 HTTPS
NameVirtualHost *:80
...
NameVirtualHo
On Tue, 2009-10-27 at 07:28 +0100, André Warnier wrote:
> Krist van Besien wrote:
> > On Mon, Oct 26, 2009 at 9:01 PM, André Warnier wrote:
> >> The other way I could think of would be to use virtual hosts, like
> >>
> >> Listen 80 HTTP
> >> Listen 443 HTTPS
> >>
> >> NameVirtualHost *:80
> >>
>
On Tue, Oct 27, 2009 at 7:28 AM, André Warnier wrote:
> Krist van Besien wrote:
>>
>> On Mon, Oct 26, 2009 at 9:01 PM, André Warnier wrote:
>>>
>>> The other way I could think of would be to use virtual hosts, like
>>>
>>> Listen 80 HTTP
>>> Listen 443 HTTPS
>>>
>>> NameVirtualHost *:80
>>>
>>>
Krist van Besien wrote:
On Mon, Oct 26, 2009 at 9:01 PM, André Warnier wrote:
The other way I could think of would be to use virtual hosts, like
Listen 80 HTTP
Listen 443 HTTPS
NameVirtualHost *:80
...
NameVirtualHost *:443
... (SSL-based config)
You don't need the NameVirtualHost dire
On Mon, Oct 26, 2009 at 9:01 PM, André Warnier wrote:
>
> The other way I could think of would be to use virtual hosts, like
>
> Listen 80 HTTP
> Listen 443 HTTPS
>
> NameVirtualHost *:80
>
> ...
>
>
> NameVirtualHost *:443
>
> ... (SSL-based config)
>
You don't need the NameVirtualHost direc
André Warnier wrote:
...
and there are also some interesting tidbits here :
http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html
See for example :
How can I switch between HTTP and HTTPS in relative hyperlinks?
(I did not know this either; it's good to read the fine documentation
sometimes).
An
...@httpd] Enabling HTTP and HTTPs
Jorge Medina wrote:
> Right. I have two Listen directives
>
> Listen 80 http
> Listen 443 https
>
> The page I would assume that the page I get is generated by the mod_ssl
> module. It looks something like this:
>
Allright, that clears on
Jorge Medina wrote:
Right. I have two Listen directives
Listen 80 http
Listen 443 https
The page I would assume that the page I get is generated by the mod_ssl module.
It looks something like this:
Allright, that clears one mystery, and I learned something (I did not
know that mod_ssl was d
André Warnier [mailto:a...@ice-sa.com]
Sent: Monday, October 26, 2009 3:03 PM
To: users@httpd.apache.org
Subject: Re: [us...@httpd] Enabling HTTP and HTTPs
Hi Jorge.
Something below does not seem to square :
Jorge Medina wrote:
...
> At that point, I disabled HTTP on the server. Any request
Hi Jorge.
Something below does not seem to square :
Jorge Medina wrote:
...
At that point, I disabled HTTP on the server. Any request on port 80 gets a
page indicating that HTTPS is required.
How do they actually get this page, if HTTP is disabled ?
Maybe to gain some steps :
- the default
I am using Apache 2.2 and I am using a test certificate signed by my internal
CA. I am not using Virtual Hosts.
Sometime ago I went over a whole set of changes on my server configuration to
enable HTTPs (SSL).
At that point, I disabled HTTP on the server. Any request on port 80 gets a
page ind
12 matches
Mail list logo
