vis
emma.davi...@aol.com
-Original Message-
From: Sander Smeenk
To: users@httpd.apache.org
Sent: Sat, 8 May 2021 18:17
Subject: Re: [users@httpd] apache routing issue
Quoting emma davis (emma.davi...@aol.com.INVALID):
> When setting up virtual host I was not able give ServerAlias to
Quoting Paul Claridge (p...@vicjenmail.plus.com):
> Does the default *:80 also serve data to localhost?
Yep. Should work just like any other IP on your sytstem.
> I assumed by creating another VH that would achieve a "shortcircuit" and
> serve data to my local puppeteer browser from my prime
Quoting emma davis (emma.davi...@aol.com.INVALID):
> When setting up virtual host I was not able give ServerAlias to
> x.ddns.net
> Apachectl -S gave an error.
It would be helpful if you'd share the actual error.
> P.s. This is Emma,That is Emily with a protective Daddy, she is
> working
o: users@httpd.apache.org
Subject: Re: [users@httpd] apache routing issue
On 07/05/2021 07:02, Sander Smeenk wrote:
> Quoting emma davis (emma.davi...@aol.com.INVALID):
>
>> It is a domain name identification issue by Apache.
>> May be it a known issue.
>
> Apache has the c
May 2021 7:02
Subject: Re: [users@httpd] apache routing issue
Quoting emma davis (emma.davi...@aol.com.INVALID):
> It is a domain name identification issue by Apache.
> May be it a known issue.
Apache has the concent of a 'default' virtual host. Any request to a
domain not explicitly c
On 07/05/2021 07:02, Sander Smeenk wrote:
Quoting emma davis (emma.davi...@aol.com.INVALID):
It is a domain name identification issue by Apache.
May be it a known issue.
Apache has the concent of a 'default' virtual host. Any request to a
domain not explicitly confiugred for that ip/port
is working on a
school project
emma davis
emma.davi...@aol.com
-Original Message-
From: Sander Smeenk
To: users@httpd.apache.org
Sent: Fri, 7 May 2021 7:02
Subject: Re: [users@httpd] apache routing issue
Quoting emma davis (emma.davi...@aol.com.INVALID):
> It is a domain n
Quoting emma davis (emma.davi...@aol.com.INVALID):
> It is a domain name identification issue by Apache.
> May be it a known issue.
Apache has the concent of a 'default' virtual host. Any request to a
domain not explicitly confiugred for that ip/port combo will be handled
by the defaul virtual
Hi,
I have identified an issue but I haven't isolated it yet.
I think I have, may be.
I am going to list the steps as I pin it down and post it them
because I know there is an issue.
It is a domain name identification issue by Apache.
May be it a known issue.
Problem description:
I had two
