> Also, Apache should have reported this unclosed on restart.
Config parsing isn't file based/scoped. If you use it eats
everything until the closing even if it's from a different
Include'ed file and not what you intended.
-
T
On Fri, Oct 11, 2024 at 4:32 AM Adam Mihai Gergely
wrote:
> Hello,
>
> I have a rather wierd question about Apache Directives Configuration.
>
> I am running Ubuntu Linux Server and my Apache Tree looks like this:
>
> server [/etc/apache2] # tree
> .
> ├── apache2.conf
> ├── apache2.conf.dpkg-old
Op vrijdag 11 oktober 2024 04:39:30 CEST schreef Yehuda Katz:
> This does sound like a client-side issue (as others have mentioned),
> especially since you said it works on http://localhost/. I can give you a
> concrete suggestion: Check the browser console for errors/notices. In most
> browsers (
Hello,
I have a rather wierd question about Apache Directives Configuration.
I am running Ubuntu Linux Server and my Apache Tree looks like this:
server [/etc/apache2] # tree
.
├── apache2.conf
├── apache2.conf.dpkg-old
├── apache2.conf.in
├── conf-available
│ ├── charset.conf
│ ├── javascr
