-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app assets are not accessible behind nginx proxy on kubernetes #19
Comments
Hi, I have made a quick fix.
HTH |
@jiazhai @bbonnin
|
@rvashishth |
it didn't work for me via nginx. Though i can access the app using LoadBalancer service type. Check below the kubernetes nginx config and errors.
Error remains same. |
In my fix, I've updated the content security policy directive. |
yes. i have tested with updated build. |
Similar issue on pulsar dashboard
I have deployed
pulsar-express
on azure kubernetes services. when loading the on browser using nginx ingress controller host name, it failed to load resources. All call to resources are made using absolute path.here Pulsar-Express is deployed behind < https://cluster-host/pulsar-express > but all call to asset resources is not going via
/pulsar-express
uri, instead all call are made to absolute uri. https://cluster-host/_nuxt/576314c3783866ee5689.js instead of https://cluster-host/pulsar-express/_nuxt/576314c3783866ee5689.jsThe text was updated successfully, but these errors were encountered: