This project will serve as a SFCC Cartridge that requests can be made to in an SFCC instance instead of accessing OCAPI directly.
One may use this proxy to be middleware to seperate calls being made from a mobile app (ajax for instance)
Coresponding Cordova/PhoneGap App Template: https://github.com/johnfacey/sfcc-cordova-ocapi
Configure the OCAPI BM Settings More Documentation to follow
Required:
SFCC Instance - Configured for OCAPI
Optional:
Postman or another rest API tool.
load the int_ocapi_intercept to version and adjust the Site path
Testing with postman:
Instructions to follow
You can send OCAPI commands to your local proxy. Specify the host to make the call. Send the endpoint as the callurl header attribute. All other attributes can be sent similar to a direct OCAPI call. This ensures that the Proxy communicates with OCAPI as middleware.
Example:
This is currently a work in progress. Please report any issues you find. Latest: Fixes to logging added dates to log files. Updated contact info for Github and Twitter.
Currently Authorization and ETag headers are returned into the body from the output proxy rather than in the header. These are not needed in 19.X
- John Facey II - Lead Developer
See the LICENSE.md file for details