Bytes to be written to the stream exceed the Content-Length bytes size specified.

Hi,
I am getting this error while passing Unicode string, For example when I am screening a name
ÖMER HİRFANOĞLU
I am getting error
"Bytes to be written to the stream exceed the Content-Length bytes size specified."
How I can send this text so that it can screen without any error.
Currently I am using UTF8Encoding
UTF8Encoding encoding = new UTF8Encoding();
byte[] byte1 = encoding.GetBytes(postData);
Here is my code
string postData = "{\"entityType\":\"" + entityType + "\",\"groupId\":\"" + groupId + "\",\"providerTypes\":[\"WATCHLIST\"],\"name\":\"" + screenText + "\"}";
string msg = postData;
var contentLength = msg.Length;
UTF8Encoding encoding = new UTF8Encoding();
byte[] byte1 = encoding.GetBytes(postData);
// for the API server to decode the authorization signature
string dataToSign = "(request-target): post " + gatewayurl + "cases/screeningRequest\n" +
"host: " + gatewayhost + "\n" + // no https only the host name
"date: " + date + "\n" + // GMT date as a string
"content-type: " + "application/json" + "\n" +
"content-length: " + contentLength + "\n" +
msg;
string authorisation = "Signature keyId=\"" + apikey + "\",algorithm=\"hmac-sha256\",headers=\"(request-target) host date content-type content-length\",signature=\"" + hmac + "\"";
Best Answer
-
hmy-documentscode-v12cwc1postrequestcs.txt@ziad.abourizk,
Thank you for the information.
From the above provided information, it seems that you are using the variable 'byte1' for holding the UTF-8 encoded value. However, you are not calculating the length of this encoded value, which might be the reason for calculation of incorrect contentLength. Can you please try calculating the content length of the UTF-8 converted postData and see the outcome?
contentLength = byte1.length;
I am attaching code example (c#) file to this reply for your reference.
Hope this helps.
0
Answers
-
Thank you for the query.
Can you please confirm us the content length which is being calculated for the request body which you are sending in the POST request?
Also, can you please let us know the programing lanaguage which you are using?
0 -
Hi,
I am using C#.Net.
{"entityType":"ORGANISATION","groupId":"xxx","providerTypes":["WATCHLIST"],"name":"ERMAKSAN GEMİ VE TEKNE YAN SANAYI"}
contentLength : 151
DatatoSign:
(request-target): post /v1/cases/screeningRequest
host: rms-world-check-one-api.thomsonreuters.com
date: Mon, 01 Apr 2019 14:06:05 GMT
content-type: application/json
content-length: 151
{"entityType":"ORGANISATION","groupId":"xxx","providerTypes":["WATCHLIST"],"name":"ERMAKSAN GEMİ VE TEKNE YAN SANAYI"}authorization:
Signature keyId="xxx",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length",signature="a9BEW7NOlLWs7hpUV26EswbVUjHt/pjo57/Qfkz8Tbw="
0 -
Thank you very much. It works.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 637 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 88 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛