# CORs configuration issue

**URL:** <https://community.dreamfactory.com/t/cors-configuration-issue/110>\
**Category:** App Configuration\
**Created:** [June 21, 2014, 5:47am UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110 "2014-06-21T05:47:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![benbusse](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/benbusse/32/4_2.png) [@benbusse](https://community.dreamfactory.com/u/benbusse)\
**Post date:** [June 21, 2014, 5:47am UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/1 "2014-06-21T05:47:13Z")

</div>

Continuing the discussion from [About the App Configuration category](https://community.dreamfactory.com/t/about-the-app-configuration-category/22/2):

> [@About the App Configuration category](https://community.dreamfactory.com/t/about-the-app-configuration-category/22/2):
>
> Ben Thanks for your response, but I have followed those instructions and I still get the error in my browser.  
> I have set the “\*” and clicked on all of the response types etc. post, get , etc.  
> I also have turned on Guests and gave Guests a role with full access.

Hey Lutrent, is this the same issue you logged about Cross Origin Request Blocked…you had CORs working fine and then it stopped working for some reason? If so, Mark will follow up with you to get it sorted out.

If this is a different issue, what specific message are you getting back from the browser dev tools? Sounds like you’ve done everything correctly. You might want to double check the role associated with the guest user again to make sure permissions are correct for the service you’re calling. Also make sure that you’ve granted access to the app for that role. For a reference example, take a look at the role setup in [this tutorial](https://blog.dreamfactory.com/tutorial-angular-and-rest-made-simple).

---

<div class="post-metadata">

**Author:** ![Lutrent](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@Lutrent](https://community.dreamfactory.com/u/Lutrent)\
**Post date:** [June 21, 2014, 8:22am UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/2 "2014-06-21T08:22:19Z")

</div>

Ben,  
yes same issue about Cross Origin Request Blocked. Whats funny is that I do several ajax calls to the same server and I get no problems. When I do say the 4th call to this same server domain, I then get the Cross Origin Blocked error. This is whats thows me. If CORS wasnt working it should block all of my commands not just a few of them.  
The order in which I execute, the first 2-3 calls work. Then it breaks with the following message:  
""“Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at This can be fixed by moving the resource to the same domain or enabling CORS.”""

---

<div class="post-metadata">

**Author:** ![benbusse](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/benbusse/32/4_2.png) [@benbusse](https://community.dreamfactory.com/u/benbusse)\
**Post date:** [June 21, 2014, 4:01pm UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/3 "2014-06-21T16:01:16Z")

</div>

OK that is strange. The best thing to do is hop on a Google Hangout with someone on the support team to see what’s up. Shoot a note to [support@dreamfactory.com](mailto:support@dreamfactory.com) if you haven’t already.

Also, are you using the free hosted version of DreamFactory or did you install it? If you did an install, what version are you on?

---

<div class="post-metadata">

**Author:** ![Lutrent](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@Lutrent](https://community.dreamfactory.com/u/Lutrent)\
**Post date:** [August 22, 2014, 3:12pm UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/4 "2014-08-22T15:12:47Z")

</div>

I am using the hosted version but developing local on my machine

---

<div class="post-metadata">

**Author:** ![Mark](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/mark/32/69_2.png) [@Mark](https://community.dreamfactory.com/u/Mark)\
**Post date:** [August 22, 2014, 4:05pm UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/5 "2014-08-22T16:05:33Z")

</div>

Can I ask you a couple questions?

What are the calls? GET GET GET GET, GET GET GET POST?

Also, how long is it taking until the actually final call is made…?

Thanks,  
Mark

---

<div class="post-metadata">

**Author:** ![Lutrent](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@Lutrent](https://community.dreamfactory.com/u/Lutrent)\
**Post date:** [August 22, 2014, 11:50pm UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/6 "2014-08-22T23:50:51Z")

</div>

Well I am using swagger. In my console when I access the page it takes a good while to load all of the api\_docs etc. I really only need to access a few but all of them come and get loaded in my browser at window.df.  
Write now I have a different problem. I had not touched my data for over a month and everything was working. Now all of a sudden I am getting denied to access my db service. I am not sure why.

ARGGGHHH!!!

---

<div class="post-metadata">

**Author:** ![Mark](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/mark/32/69_2.png) [@Mark](https://community.dreamfactory.com/u/Mark)\
**Post date:** [August 23, 2014, 1:35pm UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/7 "2014-08-23T13:35:44Z")

</div>

append /web/logout to DSP url

---

<div class="post-metadata">

**Author:** ![Mark](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.dreamfactory.com/mark/32/69_2.png) [@Mark](https://community.dreamfactory.com/u/Mark)\
**Post date:** [August 26, 2014, 5:32pm UTC](https://community.dreamfactory.com/t/cors-configuration-issue/110/8 "2014-08-26T17:32:04Z")

</div>

for the access to your db service, you’re going to have to go in and make sure you give yourself GET access - I know you probably already had this, but since upgrading the schema, others have had a similar issue.

thanks
