-
Hello, i have problem with authorization from web-client. The server side is from tis examle. As i suppose, the variants with metadata is not applicable in this case. I will be glad for any suggestions. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @velesUst , You are likely going to want to work with composite metadata and set your The important bit is going to be the routing metadata, which is what tells the server how to route the incoming RSocket request. I haven't dug through the server example code you linked on StackOverflow, but just by looking at your example code, you would supply the routing metadata with your Also, the example project you listed though references socket
.requestResponse({
data: Buffer.from(JSON.stringify({
user_id: '0000',
password: 'Zero4'
})),
metadata: encodeCompositeMetadata([
[MESSAGE_RSOCKET_ROUTING, encodeRoute("signin.v1")],
]),
}) You will likely want to use You may still run into some issues, but I suspect that this will get you past the Hope that helps. |
Beta Was this translation helpful? Give feedback.
Hi @velesUst ,
You are likely going to want to work with composite metadata and set your
metadataMimeType
toMESSAGE_RSOCKET_COMPOSITE_METADATA.string
.The important bit is going to be the routing metadata, which is what tells the server how to route the incoming RSocket request.
I haven't dug through the server example code you linked on StackOverflow, but just by looking at your example code, you would supply the routing metadata with your
requestStream
as so:Also, the example project you listed though references
signin
as arequest/response
so you actually don't wantrequestStream
, butrequestResponse
.