Horizon does not propagate logout_reason messages for ajax calls

[David Lapsley]

Horizon propagates logout_reason messages by setting a "logout_reason" cookie in the response. After the user is redirected to logout, the login view is rendered, and the logout_reason appears in the message portion of the login screen.

In the case of the response to an ajax request, a redirect to logout results in the creation of a new HttpResponse in horizon.middleware.HorizonMiddleware.process_request() which is then returned to the requestor. The logout_reason cookie from the incoming response is not copied over. In this case, the logout_reason will be lost.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/83227

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/83227
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=013676583d388c0717fe405a18881b41d3155545
Submitter: Jenkins
Branch: master

commit 013676583d388c0717fe405a18881b41d3155545
Author: David Lapsley <email address hidden>
Date: Wed Mar 26 14:37:48 2014 -0700

    Propagate logout_reason messages

    For ajax requests, horizon.middleware does not currently copy the
    logout_reason cookie into newly generated redirect_responses. This
    will result in lost logout_reason messages when a user is redirected
    to logout.

    This patch adds the logout_reason cookie to the list of cookies
    copied over from the incoming response to the newly created
    outgoing response.

    Change-Id: I089eff5627f870c8b3f0b7913693231602a8f9d4
    Closes-Bug: #1298074