ASP.NET Core

The Resourcefull.AspNetCore package serves and accepts files with the status codes and headers HTTP clients expect, and turns Resourcefull's exceptions into status codes:

dotnet add package Resourcefull.AspNetCore

The endpoints in this section assume Resourcefull is registered as in Getting started, and leave out authorization and validation to stay short. Before you put any of them on the internet, read Securing file endpoints: it shows how to decide who may read and write which files.

This section covers:

• Securing file endpoints: signing people in, keeping each user to their own files, choosing file names, limiting uploads, and keeping links out of logs.
• Serving downloads: sending files with the right headers, answering conditional requests, and range requests for video players and resumable downloads.
• Accepting uploads: streaming request bodies and form files into storage, with preconditions, and raising the request size limits for large files.
• Resumable uploads: endpoints for tus clients, such as Uppy, so browsers and apps resume large uploads after a dropped connection.
• Turning exceptions into status codes: one handler that answers 404, 409, 412 and the rest.
• MVC, Razor Pages and Blazor: the same pieces in controllers, pages and Blazor components.
• The dashboard: a page, for administrators, showing the store's health and each container's usage against its limits, with the JSON endpoints behind it.
• URIs for your API: giving containers and resources the URLs your endpoints serve them at.
• Sharing files with links: links that let anyone download one file, without signing in, until they expire.
• Receiving files through links: links that let anyone upload files, within limits you set, without signing in, until they expire.