[jira] [Commented] (PROTON-879) null initial response makes cyrus challenge when it probably shouldn't

2015-05-06 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531492#comment-14531492
 ] 

ASF subversion and git services commented on PROTON-879:


Commit cb4f9b9ff6f473abd0b8db9f52f59e66c3499594 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=cb4f9b9 ]

PROTON-879: It seems cyrus needs an empty initial response instead of no
response.


> null initial response makes cyrus challenge when it probably shouldn't
> --
>
> Key: PROTON-879
> URL: https://issues.apache.org/jira/browse/PROTON-879
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Reporter: Rafael H. Schloming
>Assignee: Andrew Stitcher
> Fix For: 0.10
>
> Attachments: initial-response.patch
>
>
> See attached fix.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-879) null initial response makes cyrus challenge when it probably shouldn't

2015-06-02 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569819#comment-14569819
 ] 

ASF subversion and git services commented on PROTON-879:


Commit a9468f60c2c4fbebd50d4c79dc60224e6894708c in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a9468f6 ]

PROTON-879: Restricted this fix for only ANONYMOUS mech


> null initial response makes cyrus challenge when it probably shouldn't
> --
>
> Key: PROTON-879
> URL: https://issues.apache.org/jira/browse/PROTON-879
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Reporter: Rafael H. Schloming
>Assignee: Andrew Stitcher
> Fix For: 0.10
>
> Attachments: initial-response.patch
>
>
> See attached fix.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)