Hot answers tagged

7

So what you have actually is this: As your API ELB is in a private zone it can't be accessed from the internet. Your frontend in React.js just run in User's browser and not on the UI servers, those server just serve static files. You have two options, configure your frontend servers to redirect API calls to the API ELB or just update the API ELB to be ...


2

CORS is applied at the application layer, not the infrastructure (docker) layer. So, this has nothing to do with docker. It also has nothing to do with the axios client. Rather, your server needs to allow requests from your client by returning the correct headers via the OPTIONS method. If you're using nodejs and express, you can add something like this to ...


1

Have you considered CDNjs.com: It supports CORS headers, it is dedicated to JavaScript after all. It supports HTTP/2 as well as SPDY. The cache duration is 355 days, which is probably plenty long enough. Cloudflare is used as the CDN, they provide it to cdnjs.org for free. Adding your library is a bit more than a one-liner unfortunately as you need to ...


1

CORS is not allowing subdomains, so you need to specify them in your server configuration. If you are using NGINX (or you could use it as a proxy and solve your problem) by providing dynamic cors header response server { root /path/to/your/stuff; index index.html index.htm; set $cors ""; if ($http_origin ~* (.*\.yoursweetdomain.com)) { ...


1

This sounds like an asymmetric or n-path routing issue. Here is what is probably happening: Machine A at IP address 192.168.1.1 makes initiates a [SYN] request through the LB at 192.168.1.10. the LB then proxies the payload to Machine B at 192.168.1.2, so the payload now has source: 192.168.1.1 and has has destination: 192.168.1.2 (which used to be 192.168....


Only top voted, non community-wiki answers of a minimum length are eligible