Skip to content

Transfer Type is wrongly resolved during dataplane self registration #4686

@rafaelmag110

Description

@rafaelmag110

Bug Report

Describe the Bug

With the bi-directional transfer feature, a set of supported responseTypes was introduced in the public endpoint generation service. These supported responses types are concatened to the overall supported transferTypes of the dataplane.

Since the feature was initially proposed with the transfer types to be HttpData-PULL/Websocket, but then changed to HttpData-PULL-Websocket, some reminiscences of the first proposal where not removed.

The self registration extensions tests didn't caught this because no response types where added to the tests and "publicEndpointGeneratorService.supportedResponseTypes()" returns an empty set, so the tests worked fine.

Expected Behavior

When there are supported response types, the dataplane self registration extension should advertise to the control plane in the correct format (e.g. HttpData-PULL-Websocket)

Metadata

Metadata

Assignees

Labels

triageall new issues awaiting classification

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions