[Bug] 请求过滤不生效

[ZreXoc]

已配置请求过滤器，但过滤器未生效

预期效果：添加instructions字段到请求体
实际效果：请求体仍然无instructions字段。

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• 请求过滤器不生效 #548

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

Thank you for reporting this issue.

Analysis:

Based on my investigation of the codebase, the request filter system supports two phases and multiple binding types. Here are the key findings:

Potentially affected code:

• src/lib/request-filter-engine.ts (lines 836-862) - Body filter application only supports json_path and text_replace actions
• src/app/v1/_lib/proxy/request-filter.ts - Guard phase filter application
• src/app/v1/_lib/proxy/provider-request-filter.ts - Provider-specific filter application

Common configuration issues:

1. Incorrect Action Type: For adding/modifying body fields like instructions, you must use json_path action (not set). The set action is only for headers. From src/lib/request-filter-engine.ts:839-860, only json_path and text_replace actions are supported for body scope.

2. Binding Type Matters:

   • If bindingType = "global": Filter applies to all requests (applied in guard phase via requestFilter step)
   • If bindingType = "providers" or "groups": Filter only applies when the selected provider matches (applied in providerRequestFilter step after provider selection)

3. Execution Phase:

   • guard (default): Applied early in the pipeline, modifies session.request.message
   • final: Applied just before sending to upstream, after all provider-level overrides

To help diagnose this, please provide:

• Screenshot or description of your complete filter configuration (scope, action, target, replacement, binding type, execution phase)
• Is the filter enabled (toggle switch in edit dialog)?
• What is the bindingType setting (global, providers, or groups)?
• If using providers binding, does the selected provider match the one handling your request?

Correct configuration example for adding instructions field:

• Scope: body
• Action: json_path
• Target: instructions
• Replacement: your instruction text (can be a string or JSON object)
• Binding Type: global (or providers/groups with proper selection)
• Execution Phase: guard (default) or final
• Enabled: Yes (toggle on)

---

Automated response from Claude AI