Brought a test in accordance with the implementation. This is potentially a
compatibility problem, but the new behavior can reasonably be called a
bugfix; it's not particularly useful that &client.authenticated; returns the
username when there is authentication and "0" otherwise. (When I test the
latter case in 2.1, it gives an internal server error instead, btw.) C.f.
[bug 2653 (#2653)].