ccoenraets / force-server Goto Github PK

So I am using this in a project where I am using Force Server to run on my machine locally without having to deploy the JSForce version to SFDC. However, the problem I keep running into is that the callbacks are reversed, when I get a good response from Force-Server the err is the second parameter and the response is the first. With JSForce it is the opposite, it would be nice if these matched, and would improve the development experience. I can work on it if you're interested.

@ccoenraets You're missing a license here. Could you please specify?

When running the example server (the list of contacts), I have to reauthorize the app on my Salesforce account each time the page reloads. Is this because I'm running the server locally, or is there a way to avoid this?

As documented here, In order to get a new access_token, I need to make a regular form-submission type POST request (Content-Type: application/x-www-form-urlencoded)

However when using this proxy the POST body does not seem to reach the endpoint. No matter what data I pass in, the response is always {"error_description":"grant type not supported","error":"unsupported_grant_type"}

According to this line
https://github.com/ccoenraets/force-server/blob/master/server.js#L45

It looks like the proxy server assumes that every request body is in JSON format, which is not the case for this OAuth API.

It would be nice to merge this effort iwth ssl-force-server; as that would allow for SSL based calls: https://www.npmjs.com/package/ssl-forceserver.

Or otherwise, add functionality to support SSL.

When doing a POST or GET that returns a 503 error from the proxy, the proxy goes down for about an hour. When you go the heroku url, you get an Application Error message, instead of the welcome to force server message. Wait about an hour and the server comes back up. What is happening and how do I resolve this?

Edit: The image below is of my force-server heroku page.