Does an SSL POST request to LinkedIn that my server is listening on port 443?
When making an SSL POST to LinkedIn, does my own server need to have SSL enabled or listen on port 443 to receive a response?
I am submitting a request like this (I changed the actual code, api keys, etc.)
POST /uas/oauth2/accessToken HTTP/1.1
Host: www.linkedin.com
Referer: http://www.myserver.com/LinkedProfile
Content-Type: application/x-www-form-urlencoded
Content-Length: 265
grant_type=authorization_code&code=AQREV6hhRbPCiWbbQSjTFNGELYeaGmwf65mzn6GHRN7273ma6JEq1gjCvMU0dI0Ury4smE6LkJdI_w-VSPiCA1j58&redirect_uri=http://www.myserver.com/LinkedProfile&client_id=75jv8rkdp&client_secret=dccBktuhC
Before people jump over to me and change my question, there is no other place to ask, as StackOverflow is a LinkedIn support site and my question is about a programming call - my code is doing an SSL POST to LinkedIn, but can't agree, and I'm trying to figure out why.
So please have pity on me, and someone will just answer the question, instead of putting it on me and clicking the down arrow.
Many thanks,
Arc
source to share
I'm going to answer my own question after doing a few more tests with a different server and successfully getting responses from the LinkedIn People API. SSL on my web server itself is not required. I am assuming that PHP itself is making the correct TLS call to the LinkedIn server and receiving a response, and this is separate from the Apache server SSL settings (which I disabled). Thanks everyone for the answers.
source to share