Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C76E617375 for ; Tue, 14 Jul 2015 08:22:13 +0000 (UTC) Received: (qmail 43438 invoked by uid 500); 14 Jul 2015 08:22:13 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 43379 invoked by uid 500); 14 Jul 2015 08:22:13 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 43368 invoked by uid 99); 14 Jul 2015 08:22:13 -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; Tue, 14 Jul 2015 08:22:13 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 38DABDFC7F; Tue, 14 Jul 2015 08:22:13 +0000 (UTC) From: scop To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org Message-ID: Subject: [GitHub] activemq-artemis pull request: Set content-type to STOMP ERROR fra... Content-Type: text/plain Date: Tue, 14 Jul 2015 08:22:13 +0000 (UTC) GitHub user scop opened a pull request: https://github.com/apache/activemq-artemis/pull/77 Set content-type to STOMP ERROR frames Not setting it to directly instantiated 1.0 frames though, as content-type is not in the 1.0 spec. However the 1.0 spec does not actually forbid headers outside of the spec so it shouldn't hurt if we end up setting it for some frames sent over a 1.0 connection. You can merge this pull request into a Git repository by running: $ git pull https://github.com/scop/activemq-artemis error-contenttype Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/77.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #77 ---- commit 9dc005daa6ebfb317d722c2b48ea0ddcb98fa606 Author: Ville Skyttä Date: 2015-07-14T08:06:58Z Set content-type to STOMP ERROR frames Not setting it to directly instantiated 1.0 frames though, as content-type is not in the 1.0 spec. However the 1.0 spec does not actually forbid headers outside of the spec so it shouldn't hurt if we end up setting it for some frames sent over a 1.0 connection. ---- --- 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. ---