HTTP delivery: Support BASIC-AUTH in the HTTP delivery option.
Passing credentials via Url parameters is not compatible with standard web servers, and we should always try to be compatible with standard web server behaviour when implementing web services, yes?
This would permit securing the end-point for the Http delivery option so it does not sit open to the internet as the next underground 0-day warez site. Even if there are is no way to download files once uploaded to the end-point, and even if I wrote a robot or cron job to clean up unwanted files, I should not have to write a robot to clean up unwanted files; I should just be able to secure the end-point in Apache or IIS and be done with it, like I would any other web service end-point.
Smtp delivery options already supports the fields for the username & passwd pair, so therefore this should not be a trouble with any limits on fields.
In short: please support BASIC-AUTH so I can use standard web server functionality to secure my end-point. I'm sure your security technicians will agree that an end-point which accepts anonymous uploads is a bad idea.
Hello! We are taking the time to go through these ideas carefully so that we can inform our product roadmap. We'd love any help you can provide! Please feel free to add comments or votes at this time that will help us understand if this concern is still relevant to you, and if so, how we may improve your customer experience. Thank you!