On Sun, 2023-04-23 at 15:10 +0100, Patrick O'Callaghan wrote:
I'm 99% sure this is a problem with my Apache installation.
On my internal test server, I use virtual hosts for the various
websites I maintain (I have local test versions that are exported to
the external servers that host the public versions). And I leave the
default website (the one that you'll get if you browse to the numerical
IP address) alone, so you just see the default Apache test page.
If I look at the HTTP headers (e.g. wget -S
http://example.com/) I see
very little difference between one internal or external site versus
another (basically just the size, etag hash, date, of the particular
file being served). There's nothing that obviously says which
particular service is being accessed (Certbots thing about virtual host
config demands seems even more oddball). Apache ServerName variables
seem to be only used when Apache generates some HTML content that
specifically includes them.
If you browse to
http://bree.org.uk/ and https://bree.org.uk/
do you get the same results?
If I try web browsing your site, I get the same "books" page to either
address. There is a HTTPS connection, but it complains it's not
secure. There's no obvious indication about who issued the
certificate.
Likewise, do you get the same results with browsing for a specific
serveable file?
Likewise internally and externally? (Viewing one of your pages through
a HTML validator is one way to see what the outside world sees, if you
don't have some external proxy you can use, or a VPN.)
I'm assuming that part of the problem is *external* access to port 80,
does your ISP put something in the way of the port?
Do you have some *other* certificate already there that's confusing
things?
My own (externally hosted) website has a problem that continually
irritates me: They cache the content and serve from the cache to the
outside world. Sometimes it takes an absolute age for changed content
to flow through. No amount of reloading, or using a different browser,
or deleting and replacing files, shows the new content. Even though I
had set HTTP header parameters for short caching lifespans.
I detest non-Apache servers that falsely claim to be Apache drop-in
replacements (e.g. LiteSpeed). About all they care about is supporting
template websites (e.g. WordPress).
--
NB: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
The following system info data is generated fresh for each post:
uname -rsvp
Linux 6.2.8-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 22 19:14:19
UTC 2023 x86_64