Ryan Bloom wrote:
Hi.
The big thing about ServerName in 2.0 is that it has taken over for the Port
directive from 1.3. So, the following config means that the server
listens on 127.0.0.1, port 8080, but reports itself as foo.com on port 80.
VirtualHost 127.0.0.1:8080
ServerName
jean-frederic clere [EMAIL PROTECTED] wrote:
Ryan Bloom wrote:
Hi.
The big thing about ServerName in 2.0 is that it has taken over for the Port
directive from 1.3. So, the following config means that the server
listens on 127.0.0.1, port 8080, but reports itself as foo.com on port 80.
On Tuesday 18 December 2001 03:35 am, jean-frederic clere wrote:
Ryan Bloom wrote:
Hi.
The big thing about ServerName in 2.0 is that it has taken over for the Port
directive from 1.3. So, the following config means that the server
listens on 127.0.0.1, port 8080, but reports itself
Hello there,
I am trying to understand the VirtualHost directives for Apache 2.0,
specifically with regards to specifying the port. With ServerName directive
now able to specify ports, it brings another element into the picture. Does
it make a difference if the port is specified in the
Hi.
The big thing about ServerName in 2.0 is that it has taken over for the Port
directive from 1.3. So, the following config means that the server
listens on 127.0.0.1, port 8080, but reports itself as foo.com on port 80.
VirtualHost 127.0.0.1:8080
ServerName foo.com:80
/VirtualHost
That
