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 242A7177DD for ; Mon, 20 Apr 2015 16:21:04 +0000 (UTC) Received: (qmail 20207 invoked by uid 500); 20 Apr 2015 16:21:03 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 20152 invoked by uid 500); 20 Apr 2015 16:21:03 -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 20140 invoked by uid 99); 20 Apr 2015 16:21:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 16:21:03 +0000 Date: Mon, 20 Apr 2015 16:21:03 +0000 (UTC) From: "Dejan Bosanac (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMQ-5734) Support MQTT 3.1 silent subscription fail MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5734. -------------------------------- Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/a4fbe708 > Support MQTT 3.1 silent subscription fail > ----------------------------------------- > > Key: AMQ-5734 > URL: https://issues.apache.org/jira/browse/AMQ-5734 > Project: ActiveMQ > Issue Type: Improvement > Components: MQTT > Affects Versions: 5.11.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.12.0 > > > There's a difference in what 3.1 and 3.1.1 specs say should happen when an unauthorised subscribe happens. In 3.1, the broker don't informs the client so it just silently ignores the problem. In 3.1.1 it sends special QoS back. We currently only implement the later. We need to implement also 3.1 behaviour for older clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)