Distributed Networking & security service
Platform services for distributed apps & infrastructure
Shape Device ID
Multi-Cluster Load Balancer & API Gateway
Automated Zero-Trust & API Security
Optimized for app-to-app connectivity & security
Single pane of glass for distributed apps & infrastructure
Securely share or store information using existing workflows
Global multi-cloud network, security, load balancer/ADC
K8s ingress/egress controller, WAF, API gateway, multi-cluster service mesh
DDoS mitigation with BGP/DNS or Volterra transit
API security and WAF; acceleration with distributed load balancer/ADC
App acceleration via K8s workloads running in the Volterra global network
Platform services for a large number of edge locations
Consolidated networking and security service; connectivity to cloud via Volterra network
The scenario is:
Client --> External proxy (like a CDN) --> Volterra gateway with HTTP load balancer --> webserver
When looking at the HTTP load balancer request logs, the 'src ip' shows up as that of the proxy instead of the original client ip.
This behavior makes the security policies and analytics wrong and thus not allowing proper operation in the scenario.
see request #193768 for more details
You won't be notified about changes to this idea.