I was experimenting with a react-based dashboard that I wanted to use the Imbi API in. When the JS HTTP client makes the CORS pre-flight request on /projects/123456, it receives an unauthorized error:
I curl'd the endpoint including the private token and received a 405:
< HTTP/1.1 405 Method Not Allowed
< Date: Thu, 13 Jan 2022 13:48:12 GMT
< Content-Type: application/problem+json
< Content-Length: 152
< Connection: keep-alive
< Server: imbi/0.14.1
< Vary: Accept-Encoding
< Strict-Transport-Security: max-age=15724800; includeSubDomains
<
* Connection #0 to host imbi.aweber.io left intact
{"type": "https://imbi.aweber.io/#method-not-allowed", "status": 405, "title": "Method Not Allowed", "detail": "OPTIONS is not a supported HTTP method"}%
We probably shouldn't be requiring CORs pre-flights to be authorized requests though it does open the common questions of what the CORS policy should be.
I was experimenting with a react-based dashboard that I wanted to use the Imbi API in. When the JS HTTP client makes the CORS pre-flight request on
/projects/123456
, it receives an unauthorized error:I curl'd the endpoint including the private token and received a 405:
We probably shouldn't be requiring CORs pre-flights to be authorized requests though it does open the common questions of what the CORS policy should be.