## The symptom
Using moov-io/ach v1.34.2, calling `POST /files/create` with an ACH text body
(`Content-Type: text/plain`) returned 500 errors for both valid and invalid
files. The bypass flags `allowMissingFileHeader=true` and
`allowMissingFileControl=true` in the query string had no effect. Submitting the
same file as JSON worked fine, so the bug was specific to the raw NACHA text
path.
## Why
The maintainer reproduced it: with no file header present, the text/plain path
500'd even with the bypass flags, while JSON creation was fine. A bug in the
text body handling, not your file or your flags.
## The fix
Upgrade to v1.34.4 or later. The fix shipped in PR #1379, released in v1.34.4,
and the reporter confirmed "It's working for me". The working call looks like:
```bash
curl -XPOST 'https://example.com/files/create?allowMissingFileHeader=true&allowMissingFileControl=true' \
-H 'Content-Type: text/plain' --data-binary @file.ach
```
No change to your request needed, just the version bump.
## The general lesson
When one content type works and another 500s on the same server with the same
data, the bug is in the failing content-type's code path, not your input. Check
the project's issues for that path before re-encoding your files.