Bug 49684

Summary:	enhancement for ipv6 implementation
Product:	Apache httpd-2	Reporter:	spamik
Component:	Core	Assignee:	Apache HTTPD Bugs Mailing List <bugs>
Status:	RESOLVED LATER
Severity:	enhancement	Keywords:	MassUpdate
Priority:	P2
Version:	2.2.15
Target Milestone:	---
Hardware:	All
OS:	All

Description spamik 2010-08-01 18:24:08 UTC

Apache has 
NameVirtualHost *
VirtualHost *

But if used in dual stack ipv4 and ipv6 that could allow circuventing existing ipv4 blocks using ipv6 connection.

You could use

NameVirtualhost ipv4-1:80
NameVirtualhost ipv4-2:80
<VirtualHost ipv4-1:80 ipv4-2:8 ipv6-1 ipv6-2 ipv6-3 ipv6-4 ipv6-5>
and another vhosts without ipv6 (uwanted in this case):
<VirtualHost ipv4-1:80 ipv4-2:80>

but ipv6 hosts are numerous. Its unpractical to to list them all (fe. for easy swithing between those).

So what apache need is
Listen ipv4*:80
NameVirtualhost ipv4*
VirtualHost ipv6*

no one can if needed use 

<VirtualHost ipv6*>
or
<VirtualHost ipv4* ipv6*>
or 
<VirtualHost ipv4*>

so you can specify if you want to listen on all ipv6 or all ipv4 or all interfaces.

Comment 1 spamik 2010-08-01 18:28:36 UTC

some tasks that could be accomplished with proposed ipv4* ipv6*

Setup (IP based) virtualhost on all ipv6 interfaces but not on any ipv4 interface
Setup (name based) virtualhost on all ipv4 interfaces but not on any ipv6 interfaces

this all can be done by listing IP's, but listing few milion ipv6 in httpd.conf is not great idea...

Comment 2 spamik 2010-08-01 19:22:56 UTC

NameVirtualHost 0.0.0.0:80
<VirtualHost 0.0.0.0:80>

It also catches on ipv6 interfaces. A bug I think.
No way to have virtualhost on all ipv4 but none ipv6.

Comment 3 William A. Rowe Jr. 2018-11-07 21:08:12 UTC

Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.