Export - CSV (All fields)
Export - CSV (Current fields)
PROTON-978
Framing errors after SASL exchange when max-frame-size is configured
pn_read_frame does not validate frame offset
connecting with DIGEST-MD5 fails if buffer containing outcome and first encrypted frame is received
[proton-j] make empty frame logging actually mention that it is an empty frame.
[proton-j] empty frames are logged/traced when sent but not when received
[proton-j] freed receiver link may cause a removal from the wrong collection in the session
[SASL] Raise PN_TRANSPORT_ERROR events with correct condition for authentication failure
heartbeat/empty frame trace has spurious newline
messenger doesn't handle received multi-frame transfers
On error Proton can send an open and a close frame during the SASL negotiation (before sending the AMQP header)
On error Proton can send an open and a close frame before sending the AMQP header
[python] pip installed binding fails to find correct libqpid-proton.soPROTON-957
[proton-j] make trace logging of transfer frames more useful
[proton-j] avoid some overhead when sending frames if the trace logging isnt enabled and there is no frame tracer
[proton-j] only the payload for the current frame, and not the entire remainder for the delivery, should be handed to the trace logging / frame tracer
miscelaneous cleanup
Make install fails when building Proton-C with python 3.4
SASL PLAIN over cleartext should be supported
deprecate stale methods on the Message
add ability to set a default state for settling received deliveriesPROTON-943
Bump library (.so) major version for proton-c libraries
provide the session initial incoming window via Begin rather than sending a separate Flow
[SSL] Regression: binding a transport erases the configured peer name
update session outgoing window handling
drop Java 6 support and move to targetting Java 7
Build tests fail if Java is not available
Cyrus SASL GSSAPI plugin can error if sent long buffers.
Document platform-specific usage of certificates and trust stores.
proton-j: unable to determine if LINK_REMOTE_DETACH happened in response to a local detach
[SASL] If both client and server specify ANONYMOUS mech connection setup does not complete
Cancellable tasks
proton-c seems to treat unspecified channel-max as implying 0
[SASL] PN_TRANSPORT_ERROR event not raised
[python] setup.py fails to build bindings if qpid-proton-c-devel installed
[C windows] compile warnings: PN_WINAPI defined multiple times
frames on invalid channel crash proton
make C impl behave like java wrt channel_max error
[SASL] buffer underrun if no mechs specified by peer
[SASL] pn_sasl_config_name - name gets overwritten in python binding
Incompatible protocol header handled incorrectly
SSL.peer_hostname does not return the proper value.
Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfaultPROTON-911
Implement SASL security layer
Use swig as a build dependency when possible
Qpid Proton Point to Point Hang on CentOS 6 pn_messenger_send
Would be nice to make durable subscriptions simpler
Remove dependency on libuuid
UUID version should be in sixth octet
No constants defined for Terminus.expiry_policy
Unnecessary relative path in include