[ https://issues.apache.org/jira/browse/QPID-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464735#comment-15464735 ]
Alex Rudyy edited comment on QPID-7382 at 9/5/16 10:56 AM: ----------------------------------------------------------- Lorenz, The latest changes include URL encoded queue name into a disposition file name. I think that might not be cross-browser supported. Appendix D of [RFC6266|https://tools.ietf.org/html/rfc6266] provides some recommendations about generation of Content-Disposition. It seems that filename should only include non-ASCII characters excluding percent character followed by two hexadecimal. I think that we need to include filename* into Content-Disposition when non-ASCII characters are present in the queue name was (Author: alex.rufous): Lorenz, The latest changes include URL encode queue name into a disposition file name. I think that might not be cross-browser supported. Appendix D of [RFC6266|https://tools.ietf.org/html/rfc6266] provides some recommendations about generation of Content-Disposition. It seems that filename should only include non-ASCII characters excluding percent character followed by two hexadecimal. I think that we need to include filename* into Content-Disposition when non-ASCII characters are present in the queue name > Message dialogue tries to inline the text of a text message content > regardless of the its length > ------------------------------------------------------------------------------------------------ > > Key: QPID-7382 > URL: https://issues.apache.org/jira/browse/QPID-7382 > Project: Qpid > Issue Type: Bug > Components: Java Broker > Affects Versions: 0.30, 0.32, qpid-java-6.0 > Reporter: Keith Wall > Assignee: Lorenz Quack > Fix For: qpid-java-6.1, qpid-java-6.0.5 > > Attachments: suggested-changes.diff > > > When viewing a message through the WMC, if the message's mime type indicates > that the content it text, the message dialogue tries to inline the content, > properly escaping the content first. If the content is very large, this > approach is problematic and can cause formatting problems with buttons out of > reach, or at worst an unresponsive or crashed client side UI. > The WMC should display the leading portion of a long text message using > ellipses and offer a download button to retrieve the full text content. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org