You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/05/31 21:35:00 UTC
[jira] [Commented] (ARTEMIS-4294) Support text WebSocket encoding
[ https://issues.apache.org/jira/browse/ARTEMIS-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728145#comment-17728145 ]
ASF subversion and git services commented on ARTEMIS-4294:
----------------------------------------------------------
Commit c4501f6793ab0e59e88bf6c4dba06b39ade84889 in activemq-artemis's branch refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c4501f6793 ]
ARTEMIS-4294 support text-encoded WebSocket frames
> Support text WebSocket encoding
> -------------------------------
>
> Key: ARTEMIS-4294
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4294
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Minor
> Fix For: 2.29.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> WebSocket frames can be encoded as either [binary or text|https://datatracker.ietf.org/doc/html/rfc6455#section-11.8]. Currently the broker always encodes them as binary. The broker should support an acceptor URL parameter to change the encoding to text.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)