You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
REMOVE operation requires staging_allowed_local_path to be set, even though no local file is required #726
I'm able to PUT a file without specifying a staging_allowed_local_path (via the __input_stream__ functionality), but removing the file requires it, even though removing a file doesn't require any local storage.
changed the title [-]REMOVE operation requires `staging_allowed_local_path` to set set, even though no local file is required[/-][+]REMOVE operation requires `staging_allowed_local_path` to be set, even though no local file is required[/+]on Jan 15, 2026
Activity
[-]REMOVE operation requires `staging_allowed_local_path` to set set, even though no local file is required[/-][+]REMOVE operation requires `staging_allowed_local_path` to be set, even though no local file is required[/+]fatkobra commentedon Apr 20, 2026
Hi @nikhilsuri-db
I’m interested in fixing this.
Since the issue is assigned, are you still working on it?
If not, I can put together a small patch that keeps the local-path requirement for GET / local-file PUT, but skips it for REMOVE.
Fix: REMOVE staging operation no longer requires staging_allowed_loca…