HTTP 413 during live replication is not surfaced via replication events
Author: ajboniCreated Dec 19, 2025Updated Mar 3, 2026
Labelsenhancementbughelp-wantedtriaged
Hello, I’m trying to catch an HTTP 413 (Content Too Large) error in order to notify the user when the remote server rejects a request.
When using PouchDB live replication with CouchDB, a 413 Content Too Large response from _bulk_docs is visible in DevTools, but it is not exposed through any replication event.
I expected this information to be available in the paused(err) event, but err is always undefined.
Info
pouchdb-browser:^9.0.0- Platform: Electron
- Adapter: IndexedDB
- Server: CouchDB
Source: apache/pouchdb