Support rpc-endpoint wihout specifying a port number #471

Closed
opened 2022-11-03 12:43:32 +00:00 by vampik · 3 comments
vampik commented 2022-11-03 12:43:32 +00:00 (Migrated from gitlab.com)

Currently, if we don't specify port for RPC endpoint we have hardcoded value 80 for port.

Here:
https://gitlab.com/PBSA/peerplays/-/blob/develop/libraries/plugins/peerplays_sidechain/common/rpc_client.cpp#L47

Possibility of using RPC without port is needed

Currently, if we don't specify port for RPC endpoint we have hardcoded value 80 for port. Here: https://gitlab.com/PBSA/peerplays/-/blob/develop/libraries/plugins/peerplays_sidechain/common/rpc_client.cpp#L47 Possibility of using RPC without port is needed
bobinson commented 2023-04-19 12:13:28 +00:00 (Migrated from gitlab.com)

hi @vampik - if not actively working on it, please close as out of scope.

hi @vampik - if not actively working on it, please close as out of scope.
vampik commented 2023-04-20 05:37:53 +00:00 (Migrated from gitlab.com)

Out of scope

Out of scope
vampik commented 2023-04-20 05:38:03 +00:00 (Migrated from gitlab.com)

assigned to @vampik

assigned to @vampik
vampik (Migrated from gitlab.com) closed this issue 2023-04-20 05:38:05 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Peerplays_Blockchain/peerplays_migrated#471
No description provided.