Known issues

This list shows the known issues in the current release.

• When you use GET /matrix/{id}/status to fetch the matrix status, the server responds with a 303 redirect to the matrix result. If you are using API key authentication and your client is not configured to forward the apiKey parameter on redirect, the redirect results in an authentication error. To work around this issue, either configure your client to forward the apiKey parameter on redirect, or disable redirects and append the apiKey parameter to the resultUrl provided in the status response.

• When you use GET /matrix/{id} to fetch the matrix result, the server responds with a 303 redirect to a self-signed AWS S3 URL containing the matrix result. If you are using Bearer authentication and your client forwards the Authorization header to the AWS URL, AWS returns an error. To work around this issue, configure your client to not forward authentication headers when redirecting to a different host. Note that some clients, such as browsers, may not support this configuration.