Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

Home/Models, permissions & security/Privacy & data boundaries

Which fields reach the request body: verify with a masked sample

You need it to process material containing customer details and do not know what gets sent to the model side.

To be testedVersion and environmentChecked 2026-11-14
Host version
0.1.2-alpha.5
Status
packet capture not completed here; method only
Checked
2026-11-14
A reproducible method, not a table of 'this version sends field X'. Capture conclusions must come from your own measurement; copied ones are not trustworthy.

Approach: build fake data with known content and see whether it appears verbatim in the outbound request. Only known content works as a marker.

Build the sample

Customer: Test-A
Phone: 000-0000-0000
ID: 000000000000000000
Order: TEST-0001
Note: this sentence verifies request body content

All obviously fake placeholders. Real data cannot be recalled once it enters a request, so the sample must contain nothing real.

Capture the request

  1. Have the session read the sample and answer something simple (the customer name, say).
  2. Capture the outbound request at the same time (local HTTP proxy, or raise the host's log level).
  3. Search the body for those placeholders.

Reading the result

ResultMeansNext
All four appearThe whole file is read in and sentMask sensitive material first, or keep processing local
Some appearFields may be trimmed or chunkedFind out which; do not assume partial means safe
None appearMaybe it never read the file, or you missed the bodyConfirm it answered correctly first, or the experiment is void

Writing a useful conclusion

  • State the sample, host version, model, and which hop you captured (host to gateway, or gateway to model vendor).
  • State which fields did not appear — more informative than 'everything is sent'.
  • Never write 'masked therefore safe': masking rules leak too.

What counts as working

Check every line. All of them pass or the job is not done.

  • The sample is entirely fake
  • It answered correctly, proving it read the file
  • Every placeholder has an explicit appeared or absent note

Where it fails

Symptom, cause, what to do — written in the order it actually happens.

SymptomCauseWhat to do
It did not answer and the capture is emptyThe file may never have been read; the experiment is voidRetry with a more direct instruction; confirm reading before capturing
Cannot capture the requestThe path bypasses your machine, or TLS cannot be decryptedRead gateway-side logs, or point the base URL at a proxy you control

Sources

Verified means measured here. Compiled means every line carries a source.