I'm working on an ASP.NET Core 5 MVC upload tool for our end-users. The final destination for the file involves a 3rd party service where exposing the direct upload URL would potentially leave it open to abuse. So I'm looking at introducing a "middle-man" API to filter upload requests.
Traditionally we've stored the file in Azure blob storage after receiving it from the browser before calling an Azure function to upload the file as a separate process. I'm looking to streamline this - is it possible (and wise) to make a pass through process wherein the user uploads through a browser and our API server simultaneously sends it to the 3rd party service?
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…