Hi Mark,

This is definitely not related to Moonshine. What browser are you using?
Usually Firefox is less restrictive in case of Cors. - It's just quick
thought.

Thanks,
Piotr

pon., 6 maj 2024 o 15:51 MARK HARTNETT <m_hartn...@comcast.net> napisaƂ(a):

> Hi Piotr, Still stuck on the small bug. Below you can see I made a request
> from localhost and then from my external Tomcat server at
> www.causeLogix.com and received that same message. These are both being
> requested through Moonshine server localhost:3000.
>
> *The option Access-Control-Allow-Origin:* * needs to be in the page
> header. You mentioned using Apache Server and I have learned the it has
> configurations for control access. If you know how Moonshine sets that
> option can you let me know.
>
> I've tried everything - CORS Filter in web xml, disabling localhost Cors
> in my browser and a number other little fixes. Tomcat is integrated into
> Eclipse so it might be setting some values behind the scenes.
>
> I can add Apache server to the mix but I have so many older development
> tools it might cause problems. So if you don't have any ideas on Moonshine
> - I'll setup a clean machine and go from there.
>
> *Access to XMLHttpRequest at
> 'http://localhost:8080/rootmodel/securityCommand.flex?reqType=login&userId=randy&userPwd=steak
> <http://localhost:8080/rootmodel/securityCommand.flex?reqType=login&userId=randy&userPwd=steak>'
> from origin 'http://localhost:3000 <http://localhost:3000/>' has been
> blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present
> on the requested resource.*
>
> *Access to XMLHttpRequest at
> 'http://www.causeLogix.com/rootmodel/securityCommand.flex?reqType=login&userId=randy&userPwd=steak
> <http://localhost:8080/rootmodel/securityCommand.flex?reqType=login&userId=randy&userPwd=steak>'
> from origin 'http://localhost:3000 <http://localhost:3000/>?
> <http://localhost:3000/>' has been blocked by CORS policy: No
> 'Access-Control-Allow-Origin' header is present on the requested resosurce.*
>
>
>
>


-- 

Piotr Zarzycki

Reply via email to