Layer 7 capabilities for HTTP/HTTPS traffic
FortiADC provides full-featured support for HTTP/HTTPS traffic, combining secure protocol handling with advanced application delivery, visibility, and optimization.
Packet Processing
We will introduce FortiADC’s HTTP/HTTPS packet processing capabilities from the following perspectives:
SSL offloading (If HTTPS is used)
-
Terminates incoming HTTPS connections, decrypts the content for inspection and optimization, and optionally re-encrypts when forwarding to the back-end.
-
Acts as a secure proxy, presenting server certificates on behalf of applications—centralizing certificate management and simplifying compliance.
Supports next-gen protocols (HTTP/2 and HTTP/3), enabling multiplexing, better latency, and improved mobile performance.
Speeds up content delivery by compressing HTTP payloads (GZIP, Deflate) and decompressing if needed.
Reduces back-end load and latency by caching static or semi-static content.
FortiADC allows you to modify content within HTTP and HTTPS requests/responses using content rewriting policies. This can include:
-
Header Rewriting: Add, remove, or replace HTTP headers (e.g., Server, Set-Cookie, etc.).
-
URL Rewriting: Change URL paths or query parameters on-the-fly.
-
Redirects: Implement conditional HTTP redirects.
-
Multiple timeout settings manage every stage of HTTPS session lifecycle, from initial connection to request processing, ensuring graceful failover and efficient resource use.
-
Requests waiting due to server overload are queued and served or dropped based on queue timeout settings.
-
Can maintain session stability even when one side closes, useful in mobile or distributed environments.
-
Supports HTTP Keepalive to reuse connections for multiple requests—reducing handshake overhead and improving response time.
Advanced buffer and header tuning
Advanced options like buffer size and max header count allow tuning for high-performance or high-concurrency environments.
Maintains client IP visibility via:
-
Transparent source IP pass-through (when Client Address is enabled)
-
X-Forwarded-For header injection
Content Routing
Routing content based on HTTP Host Header, HTTP Request URL, HTTP Referer Header, Source IP address, SNI.
Load Balancing Methods
Round Robin, Least Connection, URI Hash, Full URI Hash, Host Hash, Host Domain Hash, Dynamic Load
Persistence
Source Address, Source Address Hash, Source Address-Port Hash, HTTP Header Hash, HTTP Request Hash, Cookie Hash, Persistent Cookie, Insert Cookie, Embedded Cookie, Rewrite Cookie, SSL Session ID (HTTPS only), Passive Cookie
Security Check
-
Antivirus
-
DoS prevention
-
IP Reputation
-
Geo IP-based access control
-
WAF checks including SQL/XSS injection check, signature-based inspection, anomaly detection, bot mitigation, API Protection, etc.