Better http error handling options for download plugin

Created on 30 November 2016, about 8 years ago
Updated 22 April 2024, 9 months ago

The shiny new download plugin works great for anything that returns HTTP 200... but if your file source returns any other error code, it throws an exception that ends the whole migration.

This is less than ideal. Off the top of my head, we want to allow 404s to happen at least, without blowing up the entire process.

Suggestion:

Add a configuration option to the download plugin, which allows you to define "skip row" behavior for 404s.

πŸ› Bug report
Status

Closed: duplicate

Version

11.0 πŸ”₯

Component
MigrationΒ  β†’

Last updated about 13 hours ago

Created by

πŸ‡©πŸ‡ͺGermany ohthehugemanatee

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024