Skip to content
This repository has been archived by the owner on Feb 17, 2022. It is now read-only.

did not parse error response in control.sesame #1

Open
legnoh opened this issue Sep 23, 2019 · 0 comments
Open

did not parse error response in control.sesame #1

legnoh opened this issue Sep 23, 2019 · 0 comments

Comments

@legnoh
Copy link
Owner

legnoh commented Sep 23, 2019

Response did not contain formatted error: Could not decode JSON response: json: cannot unmarshal string into Go value of type sesame.errorObject. HTTP response code: 400. Raw response: &{Status:400 Bad Request StatusCode:400 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Access-Control-Allow-Headers:[] Access-Control-Allow-Methods:[POST] Access-Control-Allow-Origin:[] Connection:[keep-alive] Content-Length:[35] Content-Type:[application/json] Date:[Mon, 23 Sep 2019 11:04:35 GMT] Via:[1.1 ebad70184cd5ce3b30f8fc580db81cf7.cloudfront.net (CloudFront)] X-Amz-Apigw-Id:[Ad7-ZF1qyK4FldQ=] X-Amz-Cf-Id:[3Os5GjL7wS2zvWZLPeOdNyNOMCV4I3BwKN4UPlc2G_PL5Ha5zNd_zQ==] X-Amz-Cf-Pop:[NRT57-C4] X-Amzn-Requestid:[a919034f-5cb2-463c-99bc-739d43de2de7] X-Amzn-Trace-Id:[Root=1-5d88a6c2-9ad281661968c00711ab3990;Sampled=0] X-Cache:[Error from cloudfront]] Body:0xc000082040 ContentLength:35 TransferEncoding:[] Close:false Uncompressed:false Trailer:map[] Request:0xc000106000 TLS:0xc0002bbc30}%

@legnoh legnoh changed the title did not parse error response did not parse error response in control.sesame Sep 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant