Use type system to prevent request validation bypasses

まず、プロキシリクエストの処理エントリポイントとRuleEngineを特定し、次にリクエストがどのように検証、変換され、upstreamに送信されるかを追跡します。issueではファイルもテストも指定されていません。完了条件は、検証後に作成可能な型だけをupstreamへの転送で受け付けること、そしてHost-headerおよび関連するbypassチェックがカバーされていることです。

Summary

We should refactor the proxy request handling to use the type system to ensure all requests passed to upstream servers have been validated by the RuleEngine, making it impossible at compile time to accidentally bypass security checks.

Background

While fixing the Host header bypass vulnerability (#57), we added runtime validation to ensure the Host header matches the URI. However, this and similar security checks could be better enforced through the type system.

Proposed Solution

Introduce type-safe request handling that guarantees validation:

// Example approach
struct ValidatedRequest {
    // Can only be constructed after passing RuleEngine validation
    inner: Request<BoxBody<Bytes, HyperError>>,
}

impl ValidatedRequest {
    // Private constructor - only RuleEngine can create these
    fn new(request: Request, validation_result: RuleEvaluation) -> Result<Self> {
        // Ensure all headers match validated URL
        // Apply any security transformations
    }
}

// Upstream client only accepts ValidatedRequest
fn send_to_upstream(request: ValidatedRequest) -> Result<Response> {
    // Impossible to send unvalidated requests
}

Benefits

1. Compile-time safety - Makes it impossible to accidentally forward unvalidated or modified requests
2. Clear security boundaries - Type system enforces that all upstream requests go through validation
3. Prevents regression - New code can't accidentally bypass security checks
4. Self-documenting - Types make security requirements explicit