When GetBucketLocation fails, use S3-classic endpoint

From the comments:

	A 403 can be caused by IAM keys that do not permit
	GetBucketLocation.  To not change behavior for environments
	that do not have GetBucketLocation allowed, fall back to the
	default endpoint, preserving behavior for those using
	S3-Classic.