Getting Started with Photo Supreme's Integrated HTTP Server
Browser Origins and CORS
Serving the pages and both APIs from the same HTTPS origin is the simplest setup. An origin is the combination of scheme, hostname, and port.
If the pages are served from https://photos.example.com but the API is at https://api.example.com, the browser performs cross-origin requests. Configure the backend's Domain Name Origin for the page origin, for example:
https://photos.example.com
Do not enter a page path such as /index.htm. A different scheme or non-default port means a different origin. Use the minimum required origin rather than loosening access to * to make an error disappear. CORS is a browser permission mechanism, not authentication or a network access restriction.
An HTTPS page must not call an HTTP API or fetch HTTP media. Browsers can block this as mixed content. Keep api.url, api.thumbsUrl, and the page URL consistent with your HTTPS deployment. Do not disable browser security as a workaround.