Drive - Connection to URL with 301 redirect defined

Scenario

There is a cloud customer who uses Drive to ingest content.  The Nuxeo site is accessible thru 2 URLs:

• https://<sitename>.nuxeocloud.com
• https://<sitename>.customerdomain.com

There is a 301 redirect defined so when a user hits the 'nuxeocloud.com' domain, it redirects to the 'customerdomain'.  Drive does not successfully connect to the 'nuxeocloud.com' domain when the 301 redirect is present.  It does connect to the 'customerdomain' url without issue.

The customer initially rolled out Drive to a lof of "consumers" with the 'nuxeocloud.com' URL, but now wants to change to the 'customerdomain.com' URL without having the users change the initial connection setup.

This is a ticket for product team review of the "requirement" of a Drive connection to a URL with a 301 redirect defined.

Attached is the error received when attempt to connect to 'nuxeocloud.com' domain with the 301 redirect in place.