We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Client Request] { host = s3.amazonaws.com:443 secure = True method = GET target = Nothing timeout = ResponseTimeoutMicro 70000000 redirects = 0 path = /com-subtlemedical-device-sharelake-prod-eu-west-1 query = ?location= SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=4517b6b7232f8c20f1d62ba43772ff6e9558b2b7ca7523560e8b4e81c03af7b8 body = } [Client Response] { status = 200 OK headers = x-amz-id-2: vBY7CTUB30zsG6GPaW3UOwhHzxT5tiQs+ft+nW2lHE4XwcClJgo0YoA8fYpuF9qUddb/Ugk4syY=; x-amz-request-id: BANZGY418D2XDWN9; date: Thu, 13 May 2021 19:22:12 GMT; content-type: application/xml; transfer-encoding: chunked; server: AmazonS3 } [Raw Response Body] { <?xml version="1.0" encoding="UTF-8"?> <LocationConstraint xmlns="http://s3.amazonaws.com/doc/2006-03-01/">eu-west-1</LocationConstraint> } [SerializeError] { service = S3 status = 200 OK message = Failure parsing LocationConstraint from "eu-west-1" body = Just <?xml version="1.0" encoding="UTF-8"?> <LocationConstraint xmlns="http://s3.amazonaws.com/doc/2006-03-01/">eu-west-1</LocationConstraint> } subtle-shared: SerializeError (SerializeError' {_serializeAbbrev = Abbrev "S3", _serializeStatus = Status {statusCode = 200, statusMessage = "OK"}, _serializeBody = Just "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<LocationConstraint xmlns=\"http://s3.amazonaws.com/doc/2006-03-01/\">eu-west-1</LocationConstraint>", _serializeMessage = "Failure parsing LocationConstraint from \"eu-west-1\""})
The text was updated successfully, but these errors were encountered:
Possibly related to #249 / #237 ?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The text was updated successfully, but these errors were encountered: