Files
clean-architecture-backend-…/docs/fileserver/http-contract.md
T
DongHyeonkaandClaude Opus 5.5 6d27356e2b refactor: 부가 기능을 capability 모듈로 포장하고 기본 조립을 web-only로 전환
설계: docs/superpowers/specs/2026-09-25-capability-module-packaging-design.md
계획/진행 기록: docs/superpowers/plans/2026-09-25-capability-module-packaging.md

- Wave 0: 규칙 고정(AGENTS.md capability 완료 기준·테스트 규칙) + 차단 결함 7건
  (compose overlay 검사, redis-sdk CI job, 적용된 V9/V13 원복 + V16, @EnableScheduling,
  messaging bridge 순서, prod 에러 상세 validator, sample loggers read-only)
- Wave 1: 데이터·보안 Critical 10건 (durable operation 25P02, operation 유스케이스 이동,
  outbox 재인코딩, Kafka TLS/SASL, 알림 트랜잭션, SNS 서명, tus checksum, GraphQL fragment,
  Redis lane, gRPC FAILED_TERMINAL)
- Wave 2: 리팩터링 잔재·실험용 자리 삭제, outbox v1 fencing(V17), 멱등성 V2 정본화
- Wave 3: 라이브러리형 코드 정리(동작하지 않는 설정·인터페이스·gate 제거, web-advanced 분리)
- Wave 4: capability 11개를 "있으면 켜짐" 모듈로 포장, 끄는 장치 제거, 기본 조립 web-only,
  qualificationBootJar 분리
- Wave 5: 빌드 로직 축소(17.2k -> 10.8k줄), sample 테스트 컨벤션 적용

삭제한 코드는 docs/capability-status.md "제거된 코드" 표에 복구 커밋(208077fd)과 함께 기록.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-25 12:49:07 +09:00

4.5 KiB

Fileserver HTTP contract

Every public endpoint is listed here. FileserverDocumentationCoverageTest scans the controllers and fails if one is missing, so this file cannot silently fall behind the code.

Public endpoints

Method Path Success Notes
POST /v1/files 201 READY, 202 VERIFYING multipart single upload
POST /v1/files:raw 201, 202 the whole request body is the file
POST /v1/files:batch 200 ordered per-part results; explicitly non-atomic
GET /v1/files/{fileId} 200 public metadata; never a content key or path
GET /v1/files/{fileId}/content 200, 206, 304 download
HEAD /v1/files/{fileId}/content 200, 304 identical headers, no body
DELETE /v1/files/{fileId} 202, 204 logical delete first
POST /v1/files/{fileId}:copy 202 create-only target
POST /v1/files/{fileId}:move 200 logical namespace change only
OPTIONS /v1/uploads 204 tus capability discovery
POST /v1/uploads 201 tus creation
HEAD /v1/uploads/{uploadId} 204 tus offset
PATCH /v1/uploads/{uploadId} 204 tus append
DELETE /v1/uploads/{uploadId} 204 tus termination
POST /v1/experimental/draft12/uploads 201 Experimental; off by default
PATCH /v1/experimental/draft12/uploads/{uploadId} 204 Experimental; off by default

Management endpoints

Reachable only where both app.fileserver-platform.enabled=true and app.fileserver-platform.admin.enabled=true, gated at the servlet chain on app.fileserver-platform.security.admin-roles, and intended for a management port rather than the public one.

Method Path
GET /internal/fileserver/storage-health
GET /internal/fileserver/capabilities
GET /internal/fileserver/orphans
POST /internal/fileserver/orphans:reconcile
POST /internal/fileserver/files/{fileId}:reverify
POST /internal/fileserver/files/{fileId}:force-delete
GET /internal/fileserver/uploads/incomplete
POST /internal/fileserver/uploads:cleanup

Status codes

Status Condition
200 metadata, full GET, batch result, move
201 file or upload created
202 verification or physical cleanup deferred
204 append, cancel, bodyless update
206 satisfiable Range
304 validator matched on GET or HEAD
400 malformed header or header combination
401 unauthenticated
403 / 404 denied, or hidden under the existence-hiding profile
409 state, offset, or lease conflict
410 expired upload resource
411 require-content-length profile with no length
412 precondition failed
413 size or quota policy violation
415 upload media type not accepted
416 unsatisfiable Range; carries the real length
422 digest, signature, or scanner rejection
429 transfer admission or rate limit
460 tus Upload-Checksum does not match that request's bytes; the chunk is discarded and the offset does not move
503 storage or scanner unavailable
504 downstream timeout
507 out of storage capacity

Failure body

Every failure answers application/problem+json with a stable code and its URN:

{
  "type": "urn:fileserver:problem:upload-offset-mismatch",
  "title": "Upload offset mismatch",
  "status": 409,
  "code": "UPLOAD_OFFSET_MISMATCH",
  "retryable": true,
  "ambiguous": false,
  "reconciliationRequired": false,
  "traceId": "..."
}

The server-side exception message never appears. ambiguous is the field a client must read before retrying: an ambiguous failure may already have taken effect.

Header contract

Header Contract
Content-Type client value is a claim; the verified type is stored separately
Content-Disposition attachment by default; scriptable types are never inline
Accept-Ranges bytes
Range single range by default; multi-range only under an explicit budget
Content-Range actual range on 206; the unsatisfied form on 416
ETag strong validator derived from the SHA-256
Last-Modified metadata publication instant, never a filesystem timestamp
Cache-Control private, no-store by default
X-Content-Type-Options always nosniff on a download
Retry-After on retryable 409, 429, 503, and 504
X-Accel-Redirect internal only; never forwarded to a client