Re: [Broker-J] HTTP management

Hi Olivier, Please note, that JIRA [1] was raised to track issue with bindings using invalid selectors. The fix is scheduled for inclusion into 7.1. Please fill free to contribute a code for the fix. As for returning 400 instead of 404 when exchange does not exist for a requested operation, you

Re: Problems with SASL and a simple client/server written in C

Addendum: Now I also noticed that the transport changed from the server-init to PN_CONNECITON_INIT... I realized i used the wrong pn_listener_accept() as well... So now I use (in the PN_LISTENER_ACCEPT event: container->connection = pn_connection();

RE: [Broker-J] HTTP management

Hello Rob, Regarding the first scenario it just feels weird that a POST returns a 404 NOT_FOUND... I think 400 would indeed make more sense. I'll have a look at the last scenario as soon as I have some time. Thanks, Olivier -Original Message- From: Rob Godfrey Sent: mercredi 29 août

Problems with SASL and a simple client/server written in C

Hey! This is regarding the Qpid Proton C-API and version 0.24.0 and Cyrus SASL 2.1.26-21 running on CentOS7. I am new to the AMQP world, hance also to Qpid Proton. I am looking into implementing a good single-sign-on solution using Kerberos GSSAPI between two very simple softwares as a

Re: [VOTE] Release Qpid for Java 6.1.7

+1 Compiled from source Ran bdb and mms 0-9-1 and 0-10 test profiles Started up the broker and poked around the management console a bit -- Rob On Thu, 30 Aug 2018 at 09:57, Keith W wrote: > On Tue, 28 Aug 2018 at 13:27, Oleksandr Rudyy wrote: > > > > Hi all, > > > > I built a release

Re: [VOTE] Release Qpid for Java 6.1.7

On Tue, 28 Aug 2018 at 13:27, Oleksandr Rudyy wrote: > > Hi all, > > I built a release candidate for 6.1.7 version of the Qpid for Java. > Please give it a test out and vote accordingly. +1. My testing was: * Verified signatures and checksums * Checked for LICENCE and NOTICE files in the