[Bug 1750356] Re: Apache2: BalancerMember worker hostname (65.character.host.name) too long

Andreas Hasenack andreas at canonical.com
Wed Jun 27 18:26:43 UTC 2018

** Description changed:

+ [Impact]
+  * An explanation of the effects of the bug on users and
+  * justification for backporting the fix to the stable release.
+  * In addition, it is helpful, but not required, to include an
+    explanation of how the upload fixes this bug.
+ [Test Case]
+  * detailed instructions how to reproduce the bug
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
+ [Regression Potential]
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
+ [Other Info]
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
+  * and address these questions in advance
+ == Original Description ==
  If the BalancerMember directive contains a URL with a hostname longer
  than X characters, we fail as follows:
  BalancerMember worker hostname (65.character.host.name) too long
  The size of the hostname needs to be raised so it is RFC1035 compliant.
  Bug fixed upstream at
  https://bz.apache.org/bugzilla/show_bug.cgi?id=62085, patches backported
  to v2.4.30:
  (Both patches required, first is extended by second).

You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.

  Apache2: BalancerMember worker hostname (65.character.host.name) too

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list