You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2020/10/28 21:03:00 UTC
[jira] [Updated] (RATIS-1115) NettyServerStreamRpc should handle
error cases like duplicate headers.
[ https://issues.apache.org/jira/browse/RATIS-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rui Wang updated RATIS-1115:
----------------------------
Description:
Current server does
{code:java}
if (Header) {
streams.computeIfAbsent(request.getStreamId(), id ->createStream());
...
}
{code}
It is possible that clients send multiple headers so the entry already exists. We might choose to send a error reply without accepting duplicated headers.
was:
Current server does
if (Header) {
streams.computeIfAbsent(request.getStreamId(), id ->createStream).
...
}
It is possible that clients send multiple headers so the entry already exists. We might choose to send a error reply without accepting duplicated headers.
> NettyServerStreamRpc should handle error cases like duplicate headers.
> -----------------------------------------------------------------------
>
> Key: RATIS-1115
> URL: https://issues.apache.org/jira/browse/RATIS-1115
> Project: Ratis
> Issue Type: Sub-task
> Reporter: Rui Wang
> Assignee: Rui Wang
> Priority: Major
>
> Current server does
>
> {code:java}
> if (Header) {
> streams.computeIfAbsent(request.getStreamId(), id ->createStream());
> ...
> }
> {code}
>
>
> It is possible that clients send multiple headers so the entry already exists. We might choose to send a error reply without accepting duplicated headers.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)