OrcaSlicer HTTPS print-host preview (v0.2.2)
Pre-release
OrcaSlicer 2.4.2 can send a sliced plate through Bambu Bridge's HTTPS Octo/Klipper print-host adapter. Settings → OrcaSlicer creates a separate revocable key scoped to one printer, with copyable connection fields. Upload-only is the default; explicitly permitted upload-and-print uses a fixed AMS mapping or one external spool and enters the existing validated job lifecycle.
Keys are hashed at rest, HTTPS-only and rejected by the main API. The adapter preserves slice bytes, uses unique SD filenames, and rejects unsupported plate selections, malformed/oversized containers, busy/offline printers and changed certificate identity. No proprietary networking DLL is distributed or replaced.
Preview limits: one sliced plate at position 1; native Orca AMS sync/device controls are separate. Camera, live 3D and controls remain in the bridge dashboard. A physical print from the installed Orca UI has not been performed; release checks do not start production prints.
Validation: API authorization/upload tests, a real FTPS transfer to a disposable TLS server, Ruff and mypy passed. Isolated Chromium exercised real HTTPS key create/copy/connection-test/revoke and fixed mapping at 320/1440/3840 pixels with no overflow or JavaScript errors. Source and package credential scans found no secrets. Full Python 3.12/3.13 CI passed: 887 passed and 9 skipped in each run. The deployed dashboard also passed create/connection-test/revoke at 320/1440/3840 pixels over the actual trusted HTTPS endpoint with normal certificate validation; existing phone pairing was preserved.