[
https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532459#comment-15532459
]
Lorenz Quack edited comment on QPID-7379 at 9/29/16 10:57 AM:
--------------------------------------------------------------
I'm afraid the last commit is not doing the right thing.
According to [Appendix D of RFC
6266|https://tools.ietf.org/html/rfc6266#appendix-D] on should not use
non-ASCII (together with some other restrictions) in the filename of the
Content-Disposition header.
If there are non-ASCII characters one should replace or remove them and add a
"filename*" (notice the star at the end) field.
I suggested to look at {{AbstractQueue$MessageContent}} (actually it is now in
{{AbstractQueue$BaseMessageContent#getContentDisposition}}) which tries to take
care of all of this. Ideally we would share the code.
was (Author: lorenz.quack):
I'm afraid the last commit is not doing the right thing.
According to Appendix D of RFC 6266 on should not use non-ASCII (together with
some other restrictions) in the filename of the Content-Disposition header.
If there are non-ASCII characters one should replace or remove them and add a
"filename*" (notice the star at the end) field.
I suggested to look at {{AbstractQueue$MessageContent}} (actually it is now in
{{AbstractQueue$BaseMessageContent#getContentDisposition}}) which tries to take
care of all of this. Ideally we would share the code.
> [Java Broker] Provide a mechanism to extract messages from a vhost message
> store and replay them into a new vhost
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7379
> URL: https://issues.apache.org/jira/browse/QPID-7379
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> QPID-7359 provided operations to extract the config from a virtual host, but
> there are not currently any mechanisms to extract the contents of the message
> store and replay that into a new vhost. We should add this feature to (for
> example) allow people to migrate their data from one vhost type to another
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
