On Fri, Oct 8, 2010 at 2:03 PM, Grant wrote:
>>> Strange that https URLs don't work in Opera without ServerName isn't
>>> it? They work in firefox.
>>
>> Can you elaborate on "don't work"?
>
> Yes, if I remove ServerName from my apache2 config files entirely,
> Firefox behavior doesn't change but
>> Strange that https URLs don't work in Opera without ServerName isn't
>> it? They work in firefox.
>
> Can you elaborate on "don't work"?
Yes, if I remove ServerName from my apache2 config files entirely,
Firefox behavior doesn't change but if Opera is directed to load an
https page it displays
> Strange that https URLs don't work in Opera without ServerName isn't
> it? They work in firefox.
Can you elaborate on "don't work"?
--
Eric Covener
cove...@gmail.com
-
The official User-To-User support forum of the Apache HT
actually, it's a good item to have in the vhost, the server uses it to
present names in the urls instead of ip addresses
>>>
>>> I'm surprised it's necessary since I'm not using name-based virtual
>>> hosting. Should I have ServerName in the port 80 vhost blocks or is
>>> it sufficient i
actually, it's a good item to have in the vhost, the server uses it to
present names in the urls instead of ip addresses
>>>
>>> I'm surprised it's necessary since I'm not using name-based virtual
>>> hosting. Should I have ServerName in the port 80 vhost blocks or is
>>> it sufficient i
>>> actually, it's a good item to have in the vhost, the server uses it to
>>> present names in the urls instead of ip addresses
>>
>> I'm surprised it's necessary since I'm not using name-based virtual
>> hosting. Should I have ServerName in the port 80 vhost blocks or is
>> it sufficient in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grant wrote:
>>>
>> actually, it's a good item to have in the vhost, the server uses it to
>> present names in the urls instead of ip addresses
>
> I'm surprised it's necessary since I'm not using name-based virtual
> hosting. Should I have ServerNa
>> It was ServerName. I had ServerName defined as www.example1.com in
>> Gentoo's /etc/apache2/vhosts.d/default_vhost.include. I removed it
>> from there and added it to each of my SSL VirtualHost blocks and now
>> everything works. I noticed that removing ServerName entirely works
>> for Firefo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grant wrote:
> It was ServerName. I had ServerName defined as www.example1.com in
> Gentoo's /etc/apache2/vhosts.d/default_vhost.include. I removed it
> from there and added it to each of my SSL VirtualHost blocks and now
> everything works. I noti
>> I'm sorry that this message is not as detailed as it could be. This
>> is my third attempt at sending it. It keeps tripping the spam filter,
>> probably because of all the IP and domain references.
> odd, the list isn't configured to trip on ip or domain references. must
> be a glitch somewher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grant wrote:
>>>
>>> ...
>>> SSLCertificateFile /etc/apache2/ssl/www.example1.com.crt
>>> SSLCertificateKeyFile /etc/apache2/ssl/www.example1.com.key
>>> ...
>>>
>>>
>>>
>>> ...
>>> SSLCertificateFile /etc/apache2/ssl/www.example2.com.crt
>>> SSLCer
>>
>> ...
>> SSLCertificateFile /etc/apache2/ssl/www.example1.com.crt
>> SSLCertificateKeyFile /etc/apache2/ssl/www.example1.com.key
>> ...
>>
>>
>>
>> ...
>> SSLCertificateFile /etc/apache2/ssl/www.example2.com.crt
>> SSLCertificateKeyFile /etc/apache2/ssl/www.example2.com.key
>> ...
>>
>
> no
On 2010-10-04 21:39, Rainer Jung wrote:
> I think you can define the contents of the VirtualHost
> container by a macro, but not the container itself, so e.g.
Nah. I'm defining a whole bunch of virtual hosts by macros. It works
just fine. Must be some other limitation you were thinking about.
Re
Grant wrote:
>
> ...
> SSLCertificateFile /etc/apache2/ssl/www.example1.com.crt
> SSLCertificateKeyFile /etc/apache2/ssl/www.example1.com.key
> ...
>
>
>
> ...
> SSLCertificateFile /etc/apache2/ssl/www.example2.com.crt
> SSLCertificateKeyFile /etc/apache2/ssl/www.example2.com.key
> ...
>
no
> You should use separate IPs as a best practice. As for your last
> threaded discussion concerning how you serve the correct SSL cert for
> each domain please see this article about mod_gnutls:
>
> http://www.g-loaded.eu/2007/08/10/ssl-enabled-name-based-apache-virtual-hosts-with-mod_gnutls/
>
> C
Grant,
You should use separate IPs as a best practice. As for your last
threaded discussion concerning how you serve the correct SSL cert for
each domain please see this article about mod_gnutls:
http://www.g-loaded.eu/2007/08/10/ssl-enabled-name-based-apache-virtual-hosts-with-mod_gnutls/
Craig
>> I need to set up SSL certificates for multiple domain names on a
>> single server. I've done some research and I think these are my
>> options:
>>
>> 1. use multiple IPs
>> drawbacks: requires separate apache2 config for each SSL domain, extra
>> IPs must be allocated by the hosting company
>>
- "Rainer Jung" wrote:
> On 04.10.2010 21:00, Igor Galić wrote:
> >
> > - "Grant" wrote:
> >
> The "virtualhost for each SSL host" is what I mean by separate
> apache2
> configs. I'd like to be able to define different domain names
> on
> >> the
> fly within my perl
On 04.10.2010 21:00, Igor Galić wrote:
- "Grant" wrote:
The "virtualhost for each SSL host" is what I mean by separate
apache2
configs. I'd like to be able to define different domain names on
the
fly within my perl scripts without changing apache2 config. Maybe
we're just not there ye
>> >> The "virtualhost for each SSL host" is what I mean by separate
>> >> apache2
>> >> configs. I'd like to be able to define different domain names on
>> the
>> >> fly within my perl scripts without changing apache2 config. Maybe
>> >> we're just not there yet?
>> >
>> > You can also use thing
- "Grant" wrote:
> >> The "virtualhost for each SSL host" is what I mean by separate
> >> apache2
> >> configs. I'd like to be able to define different domain names on
> the
> >> fly within my perl scripts without changing apache2 config. Maybe
> >> we're just not there yet?
> >
> > You ca
>> The "virtualhost for each SSL host" is what I mean by separate
>> apache2
>> configs. I'd like to be able to define different domain names on the
>> fly within my perl scripts without changing apache2 config. Maybe
>> we're just not there yet?
>
> You can also use things like mod_macro to enab
- "Grant" wrote:
> >> I need to set up SSL certificates for multiple domain names on a
> >> single server. I've done some research and I think these are my
> >> options:
> >>
> >> 1. use multiple IPs
> >> drawbacks: requires separate apache2 config for each SSL domain,
> extra
> >> IPs must
>> I need to set up SSL certificates for multiple domain names on a
>> single server. I've done some research and I think these are my
>> options:
>>
>> 1. use multiple IPs
>> drawbacks: requires separate apache2 config for each SSL domain, extra
>> IPs must be allocated by the hosting company
>>
On Fri, Oct 1, 2010 at 11:04 PM, Grant wrote:
> I need to set up SSL certificates for multiple domain names on a
> single server. I've done some research and I think these are my
> options:
>
> 1. use multiple IPs
> drawbacks: requires separate apache2 config for each SSL domain, extra
> IPs must
I need to set up SSL certificates for multiple domain names on a
single server. I've done some research and I think these are my
options:
1. use multiple IPs
drawbacks: requires separate apache2 config for each SSL domain, extra
IPs must be allocated by the hosting company
2. use multiple ports
26 matches
Mail list logo
