Closed robertlevy closed 7 years ago
confirmed, WAF blocking it. Looking into it to see how to whitelist.
Two Issues:
1) WAF seg faulted due to HTTP2 calls after the route change ====> this was resolved; recompiled WAF using HTTP2 branch and applied a few patches that resolved this issue. 2) Routes as mentioned above not handling properly ====> this has been identified specifically towards LB
In regards to Issue #2, missing configuration on Load Balancer. Applied to all regions.
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
we recently switched from hash routes (https://dev.calproc.website/#login) to more traditional path routes (https://dev.calproc.website/login) because the accessibility testing tool was complaining
this is working fine when running the node server locally but navigating to one of the deployed environments results in an error:
do we need to change something in a firewall, proxy server, or maybe the docker config to allow these URLs through?