Frankie Dintino

Sorry, I have been out on paternity leave. I will try to take a look at this PR some time this week.

Could you provide more information so that I might try to reproduce this issue? We have a [test to confirm whether autocomplete works, both for extra and newly added inlines](https://github.com/theatlantic/django-nested-admin/blob/68353ae81ff5afd0161fd76db56642ed813089f2/nested_admin/tests/admin_widgets/tests.py#L403-L427),...

Yes, I think this whole thing needs to be rewritten as a request body filter module. It's already not able to be used with other protocols (such as `uwsgi_pass` or...

@vkholodkov it is not true that the module doesn’t support http 2. There are even unit tests to ensure it functions, and we’ve been using it with http 2 for...

Are you uploading in the browser with the javascript File interface? If so, you would want to catch the error and retry the upload range that failed. This is how...

It might also be helpful to diagnose the issue if you provided a gist of the full debug log.

Is there any chance you have the directive `upload_cleanup` somewhere in your config?

Yes, @vkholodkov is right I believe. We're returning the wrong status code in that bit of code. That, combined with the `upload_cleanup 400 404 500-599` directive, are causing the file...

Hmmm.... one other thing. Are you sure you recompiled the module with debug flags? I don't see any of the nginx-upload-module debug messages in the log file you posted.

Could you follow the instructions for [enabling core dumps](https://docs.nginx.com/nginx/admin-guide/monitoring/debugging/#enabling-core-dumps-in-the-operating-system) and then upload the core dump somewhere I can access (e.g. dropbox)? Or, at least, paste the backtrace from the core...