Which method does the server user to respond to the requests it gets?
HTTP is request-response protocol. Irrespective of the HTTP method (GET, POST, HEAD, etc.) you use to make a request to the server, the server always responds in the same way (which has nothing to do with your request method); of course content of response is changed depending on your request.
So there's no such thing as POST or GET responses.
how is the server-upload user-download handled?
When uploading files to a server/service you're sending a request that contains the file itself, the HTTP protocol suggests that you should send data using the POST request.
When downloading files from server, the server will send you file inside the response. You should use the GET request when asking for remote files, as GET is defined as command used for retrieving resources. Also, the type of data being sent is specified in header part of both the request and response as Content-Type
.
Note that you can also upload files using GET, by stuffing the entire file into URL, or download files with response to POST request. However these are non-standard applications and have limitations (for example- limit on maximum length of URL), you would also have a lot more work on the server-side processing these requests.
Does it default to POST for large files?
This should be answered already - server does not send you any POSTs or GETs, just responses.
As a programmer how can I ensure that downloading is easy (resumable) for my end users?
This will depend on both the server-side and client-side technology used. Modern browsers and properly configured web servers generally can resume downloads of existing files automatically. However if you're building the file response manually on the server, you will also need to manually handle the download resume. See this answer for implementation with PHP.