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

ASF subversion and git services commented on DISPATCH-2209:
-----------------------------------------------------------

Commit 37087b61f12ea404d852c0187e51ef43c27bcbab in qpid-dispatch's branch 
refs/heads/main from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=37087b6 ]

DISPATCH-2209: HTTP/1.x use same meta-data keys as HTTP/2 adaptor

This closes #1312


> HTTP/1.x - fix meta-headers types and values for consistency with HTTP/2
> ------------------------------------------------------------------------
>
>                 Key: DISPATCH-2209
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-2209
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Protocol Adaptors
>    Affects Versions: 1.16.1
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Major
>             Fix For: 1.17.0
>
>
> {{The meta-data used when mapping to/from AMQP should be:}}
> {{ Message Properties Section: }}
> {{ HTTP Message         AMQP Message Properties }}
> {{ ------------         ----------------------- }}
> {{ Request Method       subject field (request message) }}
> {{ Response Status      code subject field (response message) }}
> {{ Application Properties Section: }}
> {{ HTTP Message             AMQP Message App Properties Map }}
> {{ ------------             ------------------------------- }}
> {{ Request Method           ":method": <string> }}
> {{ Message Version          ":version": <version|"1.1" by default> }}
> {{ Response Status Code     ":status": <string> (response only) }}
> {{ Response Reason          ":reason": <string> (response only) }}
> {{ Request Target           ":path": <string> }}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to