Skip to content

feat(edge): configure proxy buffers, add client X-Request-ID header, and bound trace length - #8

Merged
ATLURI0001 merged 1 commit into
mainfrom
feat/proxy-buffer-sizing-and-client-trace-header
Nov 15, 2026
Merged

ATLURI0001 merged 1 commit into
mainfrom
feat/proxy-buffer-sizing-and-client-trace-header

Conversation

@ATLURI0001

Copy link
Copy Markdown
Owner

Overview

Configures upstream proxy buffer sizing, establishes downstream client trace reflection via X-Request-ID, and bounds trace header lengths in upstream services.

Key Changes

  • Client Trace Visibility: Emits add_header X-Request-ID $request_id always; on port 443 HTTPS edge responses so clients receive the Nginx trace identifier.
  • Proxy Buffer Tuning: Explicitly configures proxy_buffering on; with dedicated buffer allocations (proxy_buffer_size 4k;, proxy_buffers 8 16k;, proxy_busy_buffers_size 32k;) in proxy.conf to prevent disk buffering on small-to-medium payload bursts.
  • Header Length Bound: Clamps incoming X-Request-ID values to 128 characters in apps/demo/app.py to prevent header overflow and memory waste.
  • Automated Invariant Verification: Expanded unit test suite in tests/test_project.py verifying response header propagation and buffer constraints.

Verification & Test Results

  • Command: python -m pytest tests/test_project.py
  • Results: 17 passed in 0.06s.
  • Exit code: 0.

Impact Analysis

  • No breaking changes to existing routing or TLS configuration.
  • Improves client observability and reduces upstream socket blocking.

@ATLURI0001
ATLURI0001 merged commit 3e5a5cd into main Nov 15, 2026
0 of 2 checks passed
@ATLURI0001
ATLURI0001 deleted the feat/proxy-buffer-sizing-and-client-trace-header branch November 15, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant