PROJECT BRIEF / 30.07.2026

1C Retail
read-only gateway

An HTTP integration gateway for operational data from 1C Retail, designed without write access to the information base.

READ-ONLY
mode
HTTP + HMAC
service
10.10.12.58:5375
supervisor
341
catalog objects
01 / OVERVIEW

One boundary for safe data access

The gateway accepts authenticated requests, passes them to a child process, and reaches V83.COMConnector. It serves receipts, sales, credit, cash operations, QR payments, and configuration knowledge.

02 / CAPABILITIES

What is covered

A

Operational data

Receipts, sales, credit operations, cash operations, and QR payments.

B

Access control

HMAC authentication, loopback child process, and read-only routes.

C

Configuration knowledge

341 objects and 1,471 explicit links, with no runtime errors or truncated samples.

D

Observability

Health, metadata, runtime, diagnostics, and signed restart.

03 / ATTENTION

Concurrent HTTP access and cached COM

ThreadingHTTPServer permits parallel worker threads while OneCClient keeps cached COM state without visible serialization or thread-local ownership. The fake-COM harness reproduced a lazy-init race in 49 of 50 runs, duplicate connections, and overlapping COM calls.

Evidence of an architectural risk, not proof of a production incident: real V83.COMConnector has not yet had a controlled read-only probe.

04 / NEXT STEP

Check - decide - then change

  1. Baseline in a safe environment.
  2. Probe serial, then 2 and 4 identical read-only requests.
  3. Compare sequential server, lock, COM worker/queue, and thread-local connections.
  4. Release only after approval, regression, staged verification, and rollback plan.