Gordon Sim commented on PROTON-915:

  1.  start wireshark
  2. run ./examples/c/messenger/recv
  3. run qpid-send --address foo

Observe wireshark trace which shows qpid-cpp sending the 0-10 header and proton 
not sending one back. If use the recv example from proton 0.8 (in a slightly 
different path, ./examples/messenger/c/recv) a protocol-header *is* sent. You 
can substitute any other tcp server using proton-c for managing protocol 
version headers in step 2, e.g. dispatch router, examples/python/broker.py etc)

> Incompatible protocol header handled incorrectly
> ------------------------------------------------
>                 Key: PROTON-915
>                 URL: https://issues.apache.org/jira/browse/PROTON-915
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.9, 0.9.1
>            Reporter: Gordon Sim
>            Assignee: Andrew Stitcher
>            Priority: Blocker
>             Fix For: 0.10
> The correct response is to send back a supported header[1] before closing the 
> socket. This worked for 0.8 but is broker from 0.9 onwards, I believe by this 
> commit: 
> https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=1b2be03c748ef5a57cf181f8373b9b6e8f8cfd22
> It means anything relying on proton-c for protocol header handling is not 
> compliant with the spec.
> [1]  section 2.2 of spec: "If the requested protocol version is not 
> supported, the server MUST send a protocol header with a supported protocol 
> version and then close the socket." 

This message was sent by Atlassian JIRA

Reply via email to