DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | adapter-inbound-web-c13 | 나중에 도는 필터가 클라이언트 값으로 덮어쓴다 | composition-and-lifecycle-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-inbound-web-c13 | 2026-09-01 |
|
|
|
adapter-inbound-web |
나중에 도는 필터가 클라이언트 값으로 덮어쓴다
두 필터 모두 서블릿 배포에서 등록되고 둘 다 X-Request-Id 응답 헤더를 쓰는데, 신뢰 정책이 반대다.
본문
두 필터 모두 서블릿 배포에서 등록되고 둘 다 X-Request-Id 응답 헤더를 쓰는데, 신뢰 정책이 반대다.
// mvc/filter/WebMvcRequestIdFilter.java:105-112 (기본 trustInboundRequestId = false)
private WebRequestId resolveRequestId(HttpServletRequest request) {
if (!trustInboundRequestId) {
return new WebRequestId(UUID.randomUUID().toString()); // 클라이언트 값을 보지 않는다
}
return sanitized(request.getHeader(REQUEST_ID_HEADER)) ...
}
WebMvcRequestIdFilter 참조 위치
:::evidence key="adapter-inbound-web-c13" alt="코드베이스에서 WebMvcRequestIdFilter 를 검색한 출력 27줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="WebMvcRequestIdFilter 코드베이스 검색 — 27줄 · exit 0" zoom="true" :::
순서가 만드는 결과
순서상 WebMvcRequestIdFilter(HIGHEST_PRECEDENCE + 10)가 먼저 돌아 새 UUID를 헤더에 쓰고, RequestLoggingFilter(LOWEST_PRECEDENCE)가 나중에 돌아 클라이언트가 보낸 값으로 덮어쓴다. MDC의 request_id와 접근 로그도 클라이언트 값이다. §32.1.