Introduction to Http Filter on Apache Dubbo

Introduction to Dubbo HttpFilter

Mon, 01 Jan 0001 00:00:00 +0000

Using HTTP to Call Dubbo

Define Pixiu Configuration File

static_resources:
 listeners:
 - name: "http-listener"
 protocol_type: "HTTP"
 address:
 socket_address:
 address: "0.0.0.0"
 port: 8888
 filter_chains:
 filters:
 - name: dgp.filter.httpconnectionmanager
 config:
 route_config:
 routes:
 - match:
 prefix: "*"
 http_filters:
 - name: dgp.filter.http.dubboproxy
 config:
 dubboProxyConfig:
 auto_resolve: true
 registries:
 "zookeeper":
 protocol: "zookeeper"
 timeout: "3s"
 address: "127.0.0.1:2181"
 username: ""
 password: ""
 timeout_config:
 connect_timeout: 5s
 request_timeout: 5s
 clusters:
 - name: "dubbo-server"
 lb_policy: "lb"
 endpoints:
 - id: 1
 socket_address:
 address: 127.0.0.1
 port: 20000
 shutdown_config:
 timeout: "60s"
 step_timeout: "10s"
 reject_policy: "immediacy"

Prepare Dubbo Service

Start zookeeper, ensure docker and compose are prepared in advance. If available locally, this can be ignored.

docker-compose.yml

Introduction to RateLimiter

Mon, 01 Jan 0001 00:00:00 +0000

Welcome to contribute to this document.

Metric Introduction

Mon, 01 Jan 0001 00:00:00 +0000

Metric Reporter Filter (dgp.filter.http.metric)

Overview

The dgp.filter.http.metric filter provides unified metric reporting for Pixiu gateway. It consolidates the functionality of two previous filters (dgp.filter.http.metric and dgp.filter.http.prometheusmetric) and supports both Pull and Push modes with OpenTelemetry integration.

Note: This filter defaults to Push mode. To use Pull mode, explicitly specify mode: "pull" in the configuration.

Key Features

Unified Entry Point: Single filter for both Pull and Push modes
OpenTelemetry Integration: Pull mode uses OpenTelemetry for metrics (consistent with Pixiu Tracing)
Context-based Extension: Other filters can record custom metrics via HttpContext.RecordMetric()
Backward Compatible: Reuses logic from original filters

Modes

Pull Mode (Recommended)

Metrics are exposed via HTTP endpoint for Prometheus to scrape.

Opa Introduction

Mon, 01 Jan 0001 00:00:00 +0000

OPA Filter (dgp.filter.http.opa)

English

Overview

The dgp.filter.http.opa filter delegates authorization decisions to Open Policy Agent (OPA) via a Rego policy. This filter evaluates requests and determines whether to allow or deny based on the policy defined in Rego. The policy is provided as an inline Rego module and evaluated using OPA’s built-in query engine.

What the filter does (current behavior)

Loads a Rego module string from config.policy.
Builds a Rego query from config.entrypoint.
For each incoming request, constructs an input object and evaluates the query.
If the query result is true, the request is allowed. Otherwise, the request is denied.

There is no built-in support for external policy files or URIs, custom HTTP status codes, or custom error bodies.

SAML Introduction

Mon, 01 Jan 0001 00:00:00 +0000

SAML Auth Filter (dgp.filter.http.auth.saml)

English

Overview

The dgp.filter.http.auth.saml filter allows Pixiu to act as a SAML Service Provider (SP).

With this filter enabled, Pixiu can:

expose SP metadata for IdP registration
redirect unauthenticated browser requests to the IdP login page
receive the SAML response on the ACS endpoint
create a session cookie after a successful login
forward selected SAML assertion attributes to upstream services as HTTP headers

Typical IdPs include Keycloak, Okta, and Microsoft Entra ID.

Circuit Breaker Introduction

Mon, 01 Jan 0001 00:00:00 +0000

Welcome to contribute to supplement this documentation.