<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integrating :: WGE</title><link>https://zhouyujt.github.io/wge/getting-started/integrating/index.html</link><description>Overview WGE is a standalone security inspection engine that does not handle network traffic directly.
By integrating WGE into a web server (such as Nginx, Apache, or Envoy), you can introduce security inspection into the request processing pipeline, enabling real-time analysis and interception of HTTP traffic.
This integration approach offers the following advantages:
Unified security enforcement at the traffic entry point (WAF capability) Seamless combination with existing reverse proxies or gateways Reuse of the web server’s logging and operations infrastructure Depending on your deployment environment, WGE supports multiple integration methods:</description><generator>Hugo</generator><language>en</language><atom:link href="https://zhouyujt.github.io/wge/getting-started/integrating/index.xml" rel="self" type="application/rss+xml"/><item><title>Integrate into Apache</title><link>https://zhouyujt.github.io/wge/getting-started/integrating/integrate-into-apache/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://zhouyujt.github.io/wge/getting-started/integrating/integrate-into-apache/index.html</guid><description>Overview The WGE Apache Connector integrates the WGE security engine into Apache HTTP Server, enabling inspection and interception of HTTP traffic during request processing.
Configuration Directives wge Syntax:
wge on | off; Scope:
rsrc, access Default:
off Description: Enables or disables WGE inspection. When set to off, WGE does not inspect requests.
wge_rules_file Syntax:
wge_rules_file &lt;path-to-rules-file>; Scope:
rsrc, access Default:
none Description: Specifies the path to the rule file to load. Ensure the Apache process user has read permission on this file.</description></item><item><title>Integrate into Envoy</title><link>https://zhouyujt.github.io/wge/getting-started/integrating/integrate-into-envoy/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://zhouyujt.github.io/wge/getting-started/integrating/integrate-into-envoy/index.html</guid><description>Overview The WGE Envoy Connector integrates the WGE security engine into Envoy as a dynamic module, enabling traffic inspection and interception during HTTP request processing.
Envoy loads external modules via its dynamic module ABI mechanism, so the WGE module must exactly match the ABI of the target Envoy version.
Prerequisites The Envoy dynamic module depends on the following ABI header files:
abi.h abi_version.h You must ensure that the ABI used when compiling the module matches the version of the running Envoy binary. A mismatch may result in:</description></item><item><title>Integrate into Nginx</title><link>https://zhouyujt.github.io/wge/getting-started/integrating/integrate-into-nginx/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://zhouyujt.github.io/wge/getting-started/integrating/integrate-into-nginx/index.html</guid><description>Overview The WGE Nginx Connector integrates the WGE security engine into Nginx, enabling inspection and interception of HTTP traffic during request processing.
Configuration Directives wge Syntax:
wge on | off; Scope:
http, server, location Default:
off Description: Enables or disables WGE inspection. When set to off, WGE does not inspect requests.
wge_rules_file Syntax:
wge_rules_file &lt;path-to-rules-file>; Scope:
http, server, location Default:
none Description: Specifies the path to the rule file to load. Ensure the Nginx process user has read permission on this file.</description></item></channel></rss>