ss it is because the default, un-vhosted server now has
NO directory entries associated with it, that is has nothing to serve,
so vhost resolution is forced.
On 27/12/2021, Jason Vas Dias wrote:
> Thanks Eric -
>
> Yes, it was DocumentRoot, a typo in my email only - sorry .
>
>
Thanks Eric -
Yes, it was DocumentRoot, a typo in my email only - sorry .
I now have ALL site in separate VHosts .
I put all the default directory entries in conf/httpd.conf into
a separate conf.d/Apache.conf :
ServerName $HOST_DNS_NAME:80
include conf.d/Apache.dir
Many thanks Eric -
Yes, I thought it must be supported ( and finally found :
https://www.oreilly.com/library/view/apache-the-definitive/0596002033/ch04s02s04.html
- "Port Based Virtual Hosts" -
) - but it is still not working.
All Port servers still serve the default Apache websites -
Good day -
I am trying to setup VirtualHosts based on Port Differences only -
is this possible ?
ie. I have, on a Centos-7 x86_64 system with apache:
httpd-2.4.6-97.el7.centos.2.x86_64
installed, in separated /etc/httpd/conf.d/*.conf files:
File conf/httpd.conf:
Listen $VPN_IP:8
On Tuesday 31 May 2011 15:37:17 Ben Timby wrote:
> On Tue, May 31, 2011 at 10:08 AM, Jason Vas Dias
> wrote:
> > I guess this is just opportunist hosts trying to connect to port 80 / port
> > 443 with a garbage protocol ?
> > If so, why are log entries made in the access
Thanks anyway - I guess I can just ignore these.
All the best,
Jason
> Dr. Larry Burton
> Associate Professor
> Department of Electronics, Computers, and Information Technology
> School of Technology
> North Carolina Agricultural and Technical State University
>
> -J
Now finally able to host a website on my home static-IP ADSL connection, using
Linux (FC-14) apache httpd-2.2.17-1.fc14.x86_64 ,
with "IP-passthrough" and "Full NAT" enabled on the ADSL router so it assigns
my host its own WAN address ,
I'm seeing these strange entries in the access log :
117.24
And, in briefly re-examing my reason for developing this module, here's
what happens when, on a stock freshly installed httpd-2.2.17-1.fc14.x86_64
FC-14 setup, I try to do :
in /etc/httpd/conf/httpd.conf :
@line 320:
#
# Possible values for the Options directive are "None", "All",
# or any
On Wednesday 06 April 2011 16:22:46 Eric Covener wrote:
> > Yes, but even with "file" the server will still "serve" those files and
> > they must still be "accessable"
> > to HTTP/S requests -
>
> It will serve them (outside of SSI) if you configure it to, but I
> don't see it as a requirement as
On Wednesday 06 April 2011 15:58:29 you wrote:
> On Wed, Apr 6, 2011 at 10:52 AM, Jason Vas Dias
> wrote:
> > I don't understand why this question got no responses .
> >
> > Surely it is not an unreasonable request to ask the server to support
> > SSI req
handler module useful, I'll post it here -
otherwise can anyone explain how else to set
up apache to allow SSI requests but NOT allow HTTP/S requests for a fragment ?
Thanks in advance for any responses (which I really do not expect to receive
after all this time on this issue ! )
and thanks
ers,
while allowing '/include/*' to be targets of SSI #include requests ?
Thanks in advance for any responses,
Regards,
Jason Vas Dias
-
The official User-To-User support forum of the Apache HTTP Server Project.
Se
12 matches
Mail list logo
