Getting a 500 when post some raw json to a triggered pipeline
I’m using postman to test the service, but also get this error when calling it through the browser.
Access-Control-Allow-Credentials →true
Access-Control-Allow-Headers →authorization, x-date, Con...
@AdrianH, when open the trigger task url with a browser, the browser is making a HTTP GET request. GET request doesn’t submit a request body. Postman can do POST request with a body.
For this 500 status case, what do you see in the pipeline run log?