Skip to content

fix(config): enforce canonical receipt origin - #5

Merged
veryCrunchy merged 1 commit into
mainfrom
fix/support-public-receipt-origin
Aug 20, 2026
Merged

fix(config): enforce canonical receipt origin#5
veryCrunchy merged 1 commit into
mainfrom
fix/support-public-receipt-origin

Conversation

@veryCrunchy

Copy link
Copy Markdown
Member

What changed

  • restore the canonical production public URL and production mode in the container and Compose defaults
  • reject unsafe production receipt origins at startup
  • keep the localhost fallback limited to development
  • verify initial, idempotent retry, and reconciled receipts use the configured canonical origin
  • clarify local and production configuration in the maintained documentation

Why

A successful intake can still be rejected by the client when the service builds receipt capability URLs from a localhost fallback. The client is correct to reject those URLs. This change fixes the server configuration boundary instead of weakening same-origin capability validation.

Validation

On the dedicated build host with Go 1.24 in Podman:

go test ./...
go build ./...
podman build --network host -t obiente-support-receipt-origin-hotfix:validation .

All Go packages passed, the backend and Vue frontend built, and the production container image completed successfully.

@veryCrunchy
veryCrunchy merged commit 5a1c45c into main Aug 20, 2026
4 checks passed
@veryCrunchy
veryCrunchy deleted the fix/support-public-receipt-origin branch August 20, 2026 16:26
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