Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9136C200BCB for ; Thu, 24 Nov 2016 13:11:38 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8E4D7160B1E; Thu, 24 Nov 2016 12:11:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D175A160B11 for ; Thu, 24 Nov 2016 13:11:37 +0100 (CET) Received: (qmail 62930 invoked by uid 500); 24 Nov 2016 12:11:37 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 62919 invoked by uid 99); 24 Nov 2016 12:11:36 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Nov 2016 12:11:36 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 99507E0AF6; Thu, 24 Nov 2016 12:11:36 +0000 (UTC) From: bostko To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-ui issue #37: request and set the csrf header protection added to b... Content-Type: text/plain Message-Id: <20161124121136.99507E0AF6@git1-us-west.apache.org> Date: Thu, 24 Nov 2016 12:11:36 +0000 (UTC) archived-at: Thu, 24 Nov 2016 12:11:38 -0000 Github user bostko commented on the issue: https://github.com/apache/brooklyn-ui/pull/37 Sorry for disturbing you I think I am wrong that this exactly broke it. Please accept that as a reminder to test logout. Logout htaccess can be broken in numerous ways... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---