Closed SudharakaP closed 4 years ago
It is not the cors policy, its the content security policy. By default (e.g. for images, videos) only self
is allowed. You need to adapt the policy accordingly. We do that already in case bootswatch themes are selected as they include parts from google fonts for example.
@atomfrede : Ah, nice; yes I was confusing the two; thanks for the explanation. 😄
Overview of the issue
This maybe due to my lack of understanding of how CORS seems to behave in JHipster applications. But I am trying to include a video in a sample jhipster application which is hosted on a external storage. Here's the sample application.
https://github.com/SudharakaP/JHipsterCORSSampleApplication
Now when I run
npm start
with Browsersync and access front-end onlocalhost:9000
everything seems to work fine. But when I run./mvnw -Pdev
it seems that the video is not accessible and I get the CORS error;Since in the
application-dev.yml
we have,I thought that in
dev
profile these requests should be allowed. Am I missing something here? 🤔Motivation for or Use Case
Making Browsersync and dev profile experience consistent.
Reproduce the error
Please clone the above repo and follow the above instructions given in the overview.
JHipster Version(s)
6.10.3
JHipster configuration