On 01/16/2013 05:38 PM, Yehuda Katz wrote:
On Wed, Jan 16, 2013 at 7:51 PM, Cecil Yother, Jr. <cj@yother.com> wrote:
The NameVirtualHost directive is obsolete, you should not set it, or rely on
it's value, for any purpose.
Pardon my ignorance, but what's taken it's place?

First, documentation for NameVirtualHost in Apache 2.4: http://httpd.apache.org/docs/2.4/mod/core.html#namevirtualhost 

The change log for Apache 2.4 notes:
The NameVirtualHost directive no longer has any effect, other than to emit a warning. Any address/port combination appearing in multiple virtual hosts is implicitly treated as a name-based virtual host. (http://httpd.apache.org/docs/2.4/upgrading.html#misc)

- Y
It appears that it's only obsolete if you're using 2.4.  If you are still using 2.2.2 NameVirtualHost is still in use.


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712


-
Forwarded by the Webmin mailing list at webadmin-list@lists.sourceforge.net
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-list