- Header values returned by the ``authtktauthenticationpolicy``

  ``remember`` and ``forget`` methods would be of type ``unicode`` if
  the ``cookie_name`` attribute was used in the ZCML declaration.
  This violated the WSGI spec, causing a ``TypeError`` to be raised
  when these headers were used under ``mod_wsgi``.

- If a routes-only BFG app was mounted under a path in modwsgi, ala
  ``WSGIScriptAlias /myapp
  /Users/chrism/projects/modwsgi/env/bfg.wsgi``, the home route (a
  route with the path of ``'/'`` or ``''``) would not match when the
  path ``/myapp`` was visited (only when the path ``/myapp/`` was
  visited).  This is now fixed: if the urldispatch root factory notes
  that the PATH_INFO is empty, it converts it to a single slash before
  trying to do matching.

1 files changed, 15 insertions, 0 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index 5af979c28..0c588a8ab 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -15,6 +15,21 @@ Bug Fixes
 - ``bfg_routesalchemy`` paster template: change ``<route>``
   declarations: rename ``renderer`` attribute to ``view_renderer``.
 
+- Header values returned by the ``authtktauthenticationpolicy``
+  ``remember`` and ``forget`` methods would be of type ``unicode`` if
+  the ``cookie_name`` attribute was used in the ZCML declaration.
+  This violated the WSGI spec, causing a ``TypeError`` to be raised
+  when these headers were used under ``mod_wsgi``.
+
+- If a routes-only BFG app was mounted under a path in modwsgi, ala
+  ``WSGIScriptAlias /myapp
+  /Users/chrism/projects/modwsgi/env/bfg.wsgi``, the home route (a
+  route with the path of ``'/'`` or ``''``) would not match when the
+  path ``/myapp`` was visited (only when the path ``/myapp/`` was
+  visited).  This is now fixed: if the urldispatch root factory notes
+  that the PATH_INFO is empty, it converts it to a single slash before
+  trying to do matching.
+
 Documentation
 -------------