ubuntu-389-directory-server team mailing list archive

[Dave Walker <davewalker@xxxxxxxxxx>]

Timo, is there any progress on this?  It should be a case of uploading
the same version to Quantal, with a higher version than the one in the
Precise queue.

To be clear, the Precise upload shouldn't be processed until the Quantal
one is ready, to at least do it in tandem.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to libapache2-mod-nss in
Ubuntu.
https://bugs.launchpad.net/bugs/1093974

Title:
  Request header field is missing ':' separator.

Status in “libapache2-mod-nss” package in Ubuntu:
  Fix Released
Status in “libapache2-mod-nss” source package in Precise:
  In Progress
Status in “libapache2-mod-nss” source package in Quantal:
  New

Bug description:
  [Impact]

  HTTPS access to 389 admin console is broken

  [Test Case]

  install 389 instance and the admin console, try accessing it over SSL

  [Regression Potential]

  low, the patch has been in Fedora for quite some time

  --

  It happens when you use SSL to access the 389 Directory server.
  When you click on the help button in the admin console, a new browser window opened and displays the error:
  Bad Request

  Your browser sent a request that this server could not understand.
  Request header field is missing ':' separator.

  Accept-Encoding/*;q=0.8

  Apache/2.2 Server at ldap.testserver.local Port 443

  It seems that this error has been fixed in Fedora and Redhat:
  https://bugzilla.redhat.com/show_bug.cgi?id=669118

  Environment:
  ubuntu 12.04 precise
  389-admin-console 1.1.8-1~ubuntu4
  389-ds-console 1.2.6-0ubuntu1
  libapache2-mod-nss 1.0.8-2~ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-nss/+bug/1093974/+subscriptions