I've tried to post utf8mb4 chars - like 🌸 - via share API to LinkedIn. But I always get 'illegal characters in XML' as response. Already tried to 'escape' it with CDATA, but it doesn't help.
When posting those chars in LinkedIn directly, it works. :-/
Any idea? Posting without those chars works without problems.
For me, posting utf8mb4 characters (like 😁) works fine if you use the json endpoint/format.
However, if you're posting XML, you need to convert them to their html entity values (e.g. 😁)... then it'll work.
Currently, LinkedIn only supports the url parameter in its share URL. So, you'll only be able to have a share button that shares a URL, not text. Like this..
https://www.linkedin.com/sharing/share-offsite/?url={url}
Source: Microsoft LinkedIn Share URL Documentation.
If you are interested in a regularly maintained GitHub project that keeps track of this so you don't have to, check us out! Social Share URLs
Related
I have a (working) custom URI scheme that opens an app in my local machine. It looks somewhat like this:
customscheme://?ip=xx.xx.xx.xx?platform=xx
I am trying to send the user a message using the Slack API including a link that opens the custom URI. It seems to work with mailto: links but not with mine.. The syntax I am trying is the following:
<customscheme://?ip=xx.xx.xx.xx?platform=xx|Open Uri>
or
[Open Uri](customscheme://?ip=xx.xx.xx.xx?platform=xx)
without success.
The thing is, I am able to create the link from the UI using the Link (Ctrl+Shift+U) functionality, pasting the exact same link from above. The outcome is exactly what I want, the text with the custom URI as the link (and it opens it after a security check).
Is there some security concern that keeps me from getting this done?
I found that inserting some word before ? then will work well
customscheme://foo?ip=xx.xx.xx.xx?platform=xx
I've tried to post an LinkedIn update with Json in .Net. Everything works fine until i use an special character. If i post "Financiën" to the API i get an "Bad Request". I've tried to htmlencode and urlencode but then i see the encoded version as an update. Has somebody solved this?
This is the request that fails:
{"comment":"Financiën","visibility":{"code":"anyone"}}
And this works:
{"comment":"Financien","visibility":{"code":"anyone"}}
I've got the answer, Linkedin needs encoding Encoding.ASCII for a post.
When I send a one-off document to RightSignature via their API, I'm specifying a callback location in the XML document as specified in RightSignature's schema definition. I then get a signer-link value back from their API for the document. I display the HTML response from the signer-link URL in an iFrame on our website. When our user signs the document in this iFrame, which is rendering the responses from their website, I want their website to post to our callback location.
Can I do this with the RightSignature API and does it make sense?
So far, I'm only getting content in the iFrame that indicates that the signing was successful. The callback location does not seem to be getting called.
I got it solved just now. Basically, i was doing two things wrong first you have to go in RightSignature Account and set it there the CallBack url
Account > Settings > Advanced Settings
But the thing which RS is unable to mention to us that this url can not be of localhost, but it should be of https i mean like Live URL of your site like
https://stagingmysite.azurewebsites.net/User/CallBackFunction
And then in your CallBack just write these two lines and you will receive complete XML which would have the GUID and document status as well.
byte[] data = Request.BinaryRead(Request.TotalBytes);
string callBackXML = System.Text.Encoding.UTF8.GetString(data);
I found the answer with some help from the API team at RightSignature. I was using callback_location but what I really wanted is redirect_location. Their online documentation was difficult to follow and did not clearly point out the difference.
I got this working after a lot of trial and error.
I am trying to get this thing to work for a couple days since it's my first time working with the OAuth system without any luck.
I have been experimenting here: https://developers.google.com/youtube/v3/docs/subscriptions/insert#try-it
With the following settings:
http://i.gyazo.com/5cd28f1194d5dfebee25d07bc0db965e.png
When I execute the code it successfully subscribes to the specified channelIdaccount with the authorized account.
I have tried to copy paste the shown POST URL into my browser without any luck. The plan was just to test it as I would like to implement this in PHP.
Now to my questions:
The {YOUR_API_KEY}, is this where I am supposed to type in the access token? If so, do I need the &mine=true tag at all?
I just realized that there are no ID's in the URL but there is an JSON-object in the request box example. Am I supposed to convert a string to JSON-object and pass it to the $fields= tag?
I have a link on a website to let users add an ICS feed to their google Calendar. Using this code:
http://www.google.com/calendar/render?cid=https://<etc>
It worked for 3-4 years but not anymore. The message Google sends me is:
This email address isn't associated with an active Google Calendar account: https://<etc>
If I enter the ics feed manually things work ok: the feed is parsed as should. No errors.
Any idea where to look to fix this?
I too have this problem. Did you solve it?
My tests show that it works when using URLs with http, like:
www.google.com/calendar/render?cid=http%3A%2%2Fwww.example.com%2FCalendar%2FPublic%2520Events.ics
But not with https, like:
www.google.com/calendar/render?cid=https%3A%2%2Fwww.example.com%2FCalendar%2FPublic%2520Events.ics
My workaround for this is to use http in the link, but redirect it to https in the web server. Not very elegant, but it works. The GET won't be encrypted, but at least the answer is.
EDIT: Actually, it can be a huge security risk sending the GET over http instead of https if you don't do any more authentication than via query string parameters, which can be hard for calendar feeds. Anyone who can sniff the GET can send the same request over https themselves.
Right now it works, even with https.
https://www.google.com/calendar/render?cid=https%3A%2F%2Fwww.example.com%2FCalendar%2FPublic%20Events.ics
Use webcal protocol for the calendar address:
https://www.google.com/calendar/render?cid=webcal%3A%2F%2Fwww.example.com%2FCalendar%2FPublic%20Events.ics
Ok, so for me, none of the other answers on this page worked. But I figured it out with bits and pieces of others:
Link to my calendar's ics:
https://example.com/calendar?id=a304036ea5a474ee5d80a100d79c231c
The right way to link it to Google Calendar:
https://calendar.google.com/calendar/r?cid=webcal%3A%2F%2Fexample.com%2Fcalendar%3Fid%3Da304036ea5a474ee5d80a100d79c231c
The key here is adding it using the webcal protocol instead of the https protocol.
Hope this helps anyone.
They got more strict.
Now you have to use
http://www.google.com/calendar/render?cid=http%3A%2F%2Fwww.example.com%2FCalendar%2FPublic%2520Events.ics
note the encoding.