Page History

As already documented above, this is the Controller (aka Listener) that the OECGI immediately calls when it receives an HTTP request. It is a replacement to RUN_OECGI_REQUEST but it is designed primarily to manage REST APIs. HTTP_MCP is a relatively small routine which fits into the SRP philosophy that controllers should be as thin as possible. The basic workflow of HTTP_MCP is as follows: 

• Call HTTP_Servicesso the HTTP request information is properly parsed so it can be easily retrieved by the rest of the API.
  
  
• Call HTTP_Authentication_Services to validate access to the entry point.
  
  
• Call the entry point service (if authorized to do so).
  
  
• Call HTTP_Services to get the HTTP response in a proper format that OECGI will accept.
   
• Capture the request and response content and store them in the designated OS folder for off-line review.
   
• Call HTTP_Services and HTTP_Authentication_Services to perform various clean-up and clearing processes to prevent future requests received by the same OpenEngine from using stale or unauthorized data.
  
  
• Return the HTTP response to the OECGI.