These are chat archives for SmingHub/Sming
For now focus on the main functionality of downloading the data and save it in a filestream with the name provided in the content-disposition header. Then we have the time to make a design decision on the callback.
There are some things to figure out. Not complete but thoughts from now :
For one or more files. Isn't that having the "upload callback/uploading" sequence more than once in the processing of the http-request ?
Thanks for the input: Actually I might need help with the filestream. I am not too familiar on how to properly use filestreams (yet). But will look into documentation and example implementations
On your thoughts:
is there a way to provide the client IP already? and why IP to prevent abuse? It would also be possible to include a password (difficult since multipart don`t necessarily have an order, so if the file is sent before the password, we need to temporarily safe it.) Or what I find better, would be to use the http basic auth. That way we can also secure other resources
I do not agree with the seperate callback - paths can have different functions in HTTP servers. It is up to the server to decide if a certain request (GET/POST) is actually valid for a path. Let`s say a user visists /upload - with a get he sees the form; with a post the data is actually uploaded to the same resource URI