@cmichael said:
First CORS errors, then 301 redirect to http insecure link...
I noticed that my search api calls were error with a CORS violation.
I noticed in the forum here that someone had success adding a trailing slash to the path just before the query string.
That worked in dev, but when I rolled out to live, where I'm using https, I now get a 301 redirect to the same url but with http instead of https and my slash before the query string removed.
Sure seems like something is messed up on the server config.
Anyone else with this issue? Could someone please advise?

I'm not a code programmer so I can't help.
But I can give links to conversations on the same CORS topic.

See if this research can help.
https://www.themoviedb.org/talk/search?advanced_search=&query=CORS&with_category=&with_status%5B%5D=closed&with_status%5B%5D=open
In some of the topics the problem was solved.
https://www.themoviedb.org/talk/5f55e3dd713ed40037f090d4
https://www.themoviedb.org/talk/5833110992514162cf03b7bd
https://www.themoviedb.org/talk/5c5dff05925141338cbce2db
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials

And this
https://www.themoviedb.org/talk/5f621eae93388b003864513c
https://www.themoviedb.org/talk/5eb07271a13533001b72740a

Looks like the problem was intermittent... and is now fixed suddenly.

Thanks though ticao2 for the help.