Timeline for REST API Unicode characters not working
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2018 at 1:07 | comment | added | PatMcClellan__c | Thanks David, it's good to have someone to bounce ideas off of. My Twilio support rep is escalating to the engineers there, so maybe they'll help me alter the header. | |
| Jan 3, 2018 at 18:37 | comment | added | David Reed |
That's definitely not a Salesforce API version. I tried some of the same tactics you're doing, too, but the requestBody is blank since it's parsed into params, and the data in params is already corrupted. I'm not sure how to work around this without access to more byte-stream manipulation than Salesforce provides. Hopefully someone else will have a good idea.
|
|
| Jan 3, 2018 at 17:06 | comment | added | PatMcClellan__c | no, I don't think I can alter what they send. I can change whether it's httpGet or httpPost, but I've tried both with no difference in what is sent into the REST API. See my question about the ApiVersion above. Is that THEIR API or Salesforce's API? I assume that's the Twilio API, as Salesforce doesn't number theirs by date. | |
| Jan 3, 2018 at 16:36 | comment | added | David Reed | @PatMcClellan, can you change the request content? Can you get delivery in JSON format, for example, or can you prepend a few bytes to the text they send? I'm curious as to whether adding a byte order mark would make a difference | |
| Jan 3, 2018 at 16:34 | comment | added | PatMcClellan__c | It appears (based on my correspondence with Twilio) that I can't change the request header. | |
| Jan 2, 2018 at 23:19 | comment | added | PatMcClellan__c | I was wrong... haven't been able to alter the Twilio-sent header to include the UTF-8 charset. Still hacking at my code, trying to see if EncodingUtil class or Blob are useful. I also tried dropping the Body text into a RichText field -- still no luck. | |
| Jan 2, 2018 at 19:21 | history | edited | David Reed | CC BY-SA 3.0 |
Corrected name of character and clarified that the encoding may be Latin-1, not UTF-16
|
| Jan 2, 2018 at 18:55 | comment | added | PatMcClellan__c | THANK YOU! I think I can write an app on my Twilio account to customize the header. At least now I know what's causing the issue. | |
| Jan 2, 2018 at 18:49 | history | answered | David Reed | CC BY-SA 3.0 |