Description
It'd be easier to work out what's happening when s3a calls against different endpoints fail if the 301 exceptions forwarded up included the URL in the header which (presumably) says where things moved to
Attachments
Issue Links
- is related to
-
HADOOP-14510 Use error code detail in AWS server responses for finer grained exceptions
- Resolved
- relates to
-
HADOOP-13674 S3A can provide a more detailed error message when accessing a bucket through an incorrect S3 endpoint.
- Resolved