On 10/19/07, Mark Drummond wrote:
>
> I have Apache sitting in front of some WebSphere app servers. So far, we
> have always used virtual hosts in Apache to give each application it's own
> FQDN. So we have app1.foo.com , app2.foo.com etc. This is leading to a
> (small) proliferation of FQDNs, and
GoDaddy offers it as an option.
I assume the cert vendor will understand what that means? I was hoping
to do the same with my ldap directory servers, one cert for
ldap.foo.com, and ldap.foo.com load balanced across the physical
boxes.
On 19/10/2007, Ajai Khattri <[EMAIL PROTECTED]> wrote:
On
I assume the cert vendor will understand what that means? I was hoping
to do the same with my ldap directory servers, one cert for
ldap.foo.com, and ldap.foo.com load balanced across the physical
boxes.
On 19/10/2007, Ajai Khattri <[EMAIL PROTECTED]> wrote:
> On Fri, 19 Oct 2007, Peter Milanese wr
On Fri, 19 Oct 2007, Peter Milanese wrote:
> As far as I know, no. Although, I've never really considered it.
You can if its a wildcard certificate.
--
Aj.
-
The official User-To-User support forum of the Apache HTTP Serve
I've never really considered it.
>
> - Original Message
> From: Mark Drummond <[EMAIL PROTECTED]>
> To: users@httpd.apache.org
> Sent: Friday, October 19, 2007 11:25:54 AM
> Subject: Re: [EMAIL PROTECTED] RE: [SPAM] - [EMAIL PROTECTED]
> application.company.com vs. w
11:16:47 AM
Subject: [EMAIL PROTECTED] RE: [SPAM] - [EMAIL PROTECTED]
application.company.com vs. www.company.com/application? - Email found in
subject
Unless you are using the load balancer ( hardware or software ) or
a load balancing scheme it shouldn't matter.
F
k Drummond [mailto:[EMAIL PROTECTED]
> *Sent:* Friday, October 19, 2007 11:09 AM
> *To:* users@httpd.apache.org
> *Subject:* [SPAM] - [EMAIL PROTECTED] application.company.com vs.
> www.company.com/application? - Email found in subject
>
>
>
> Hi all,
>
> I have Apach
007 11:09 AM
To: users@httpd.apache.org
Subject: [SPAM] - [EMAIL PROTECTED] application.company.com vs.
www.company.com/application? - Email found in subject
Hi all,
I have Apache sitting in front of some WebSphere app servers. So far, we have
always used virtual hosts in Apa
I like the cleanness of app.foo.com but you can do www.foo.com/app and
just make the URL look like app.foo.com using rewrites. I haven't
actually tried to see if that'll work with SSL though. I'd probably just
use an IP per each if you have enough IPs to do it. Keeping everything
clean will sav
Unless you are using the load balancer ( hardware or software ) or a
load balancing scheme it shouldn't matter.
From: Mark Drummond [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 11:09 AM
To: users@httpd.apache.org
Subject: [SPAM] - [EMAIL PROTECTED] application.company.c
Hi all,
I have Apache sitting in front of some WebSphere app servers. So far, we
have always used virtual hosts in Apache to give each application it's own
FQDN. So we have app1.foo.com, app2.foo.com etc. This is leading to a
(small) proliferation of FQDNs, and now I am wondering if it is better t
11 matches
Mail list logo
