Classify this thread resolved. I didn't know that HTTP was case sensitive, and
that resulted in inconsistent behavior. Just as I was about to call a priest
to exorcize a virtual machine.
* It appears that adding ServerAlias corrected the behavior.
* It is true that misuse of the telnet
I'm not sure what you are asking. No, it doesn't work. That was the one I
demonstrated in telnet. I did not get my screen filled with HTML, instead I
got an error message.
I actually copied the conf file from a working website and only renamed the
ServerName and DocumentRoot, noting else.
I'm making a guess here. Are you asking whether I assign Host: as being
example.com or www.example.com? Here's the script from each. They are
slightly different, but the result is the same.
$ telnet www.example.com 80
Trying 104.236.xxx.yyy...
Connected to example.com.
Escape character is
On January 3, 2015 at 7:36 PM, Nick Kew n...@webthing.com wrote:
On Sat, 03 Jan 2015 12:19:38 -0500
ghalvor...@hushmail.com wrote:
I'm making a guess here. Are you asking whether I assign Host:
as being example.com or www.example.com? Here's the script from
each. They are slightly
Okay, it occurred to me that I never at any point expected the file xmlprc.php
to load automatically. I would have guessed something like an index.php or
index.html to load instead. I reinstalled wordpress, but that seemed to make
no difference.
All that is in my DocumentRoot directory is a
On January 3, 2015 at 9:09 PM, Stormy storm...@stormy.ca wrote:
At 08:40 PM 1/3/2015 -0500, ghalvor...@hushmail.com wrote:
[snip]
I'm not sure why these two behave differently (www.example.com vs
example.com) I always thought the extra four letters were
something that
Apache knew how to deal
Hello,
Running Ubuntu 14.04 LTS on a Digital Ocean droplet. This machine is running
Apache/2.4.10
The /etc/apache2/apache2.conf has never been modified and is hosting a number
of sites. But there is one site that is does not load at all:
$ telnet example.com 80
Trying 104.236.25.70...