Page History

...

One source could be your web server itself (e.g., IIS, Apache, Abyss, etc.). This means the request was never handled by the OECGI, much less your API. You'll know if this is the case rather quickly because of the lack of activity on the API side. For example, you do not see new logs being generated or you do not see output coming from the command prompt running the OEngineServer. Finally, 404 responses Another sign that the 404 response was generated from web servers are typically a web server is to see if the content is HTML formatted whereas . 404 responses generated by the HTTP Framework return a RFC7807 standard problem+json media type response (see further below for examples).

In these cases it is most likely a configuration issue. The web server might not be routing the request to the OECGI properly. Go back through the Server Preparation steps. The URL Rewrite Rules can easily fail with just one minor typo.

...