This enhancement may or may not be possible. If the client machine is
connected to the network AND there is a path to the AWS server, do a cursory
connection using credentials and check for a return of 403 Forbidden response.
One possibility would be to send a GET Bucket location request.
Any response would prove connectivity, but a response returning the region
would validate the credentials.
Doing this before passing off to fuse might reduce the number of nebulus I/O
errors that user see.
Original issue reported on code.google.com by dmoore4...@gmail.com on 8 Nov 2010 at 2:58
Original issue reported on code.google.com by
dmoore4...@gmail.com
on 8 Nov 2010 at 2:58