tags 851357 wontfix
thanks
Upstream does not intend to change this behavior. See the thread starting at
http://mail-archives.apache.org/mod_mbox/httpd-dev/201702.mbox/
%3C20170202125319.GA15948%40redhat.com%3E
I won't deviate from upstream in the Debian 9 squeeze release, but I will
allow unde
On Saturday, 14 January 2017 19:36:34 CET Ondřej Surý wrote:
> Stefan,
>
> JFTR underscores in domain names are allowed, just not for hostnames. SRV,
> TLSA and other RRs make use of them.
But the character restriction for hostnames is valid for all parts of the FQDN
of a host. From RFC1035 sect
Stefan,
JFTR underscores in domain names are allowed, just not for hostnames. SRV,
TLSA and other RRs make use of them.
O.
On 14 January 2017 17:24:09 Stefan Fritsch wrote:
On Saturday, 14 January 2017 12:33:55 CET Jonathan Vollebregt wrote:
Actually that makes another point: according t
No, the *[ ... ] syntax means an arbitrary number of the thing in the
brackets.
Ah, I didn't notice the * on the line - my bad
I don't think underscores in domain names are allowed in general
Not according to the original specification:
http://www.ietf.org/rfc/rfc1034.txt
But according to
On Saturday, 14 January 2017 12:19:17 CET Jonathan Vollebregt wrote:
> Does this mean it's now impossible to create virtual hosts in apache for
> domain names with underscores?
>
> Unless they've silently added a DomainName directive somewhere this
> change breaks virtual hosts with internationa
On Saturday, 14 January 2017 12:33:55 CET Jonathan Vollebregt wrote:
> Actually that makes another point: according to RFC952 hostnames are
> allowed only a single period:
>
> http://www.ietf.org/rfc/rfc952.txt
>
> > ::= *["."]
> >::= [*[]]
>
> Unless this was updated in another
Actually that makes another point: according to RFC952 hostnames are
allowed only a single period:
http://www.ietf.org/rfc/rfc952.txt
> ::= *["."]
>::= [*[]]
Unless this was updated in another RFC that means apache shouldn't even
support subdomains in virtual hosts, and say good
It doesn't help that the apache docs on the ServerName directive seem to
use domainname and hostname interchangeably (While the restrictions you
mentioned only apply to hostnames)
> Description: Hostname and port that the server uses to identify itself
> Syntax:ServerName [scheme://]d
Hi Jonathan,
while I agree that such changes should not happen within one Debian release
and the maintainer might want to relax the rules for the package, the
ServerName accepts a hostname as a parameter and a valid hostname cannot
contain underscore. So the Apache is behaving correctly here n
Package: apache2
Version: 2.4.25-1
Severity: important
Dear Maintainer,
somewhere between 2.4.23-8 and 2.4.25-1 there was a regression that causes
apache to ignore ServerName directives containing underscores.
I have since tested and confirmed that removing the underscore fixes the
problem as do
10 matches
Mail list logo
