Okay, I’m not sure how you would get that working for Drafts without some sort of intermediary solution, or manual workaround, but hopefully someone else will have an idea of how you could do it.
Thank you for adding headers to the HTTPResponse in Drafts 25.1.4.
I was able to see all the headers, but strangely not the cookies.
I finally worked out that the server was sending the Set-Cookie header on a 302 response to my request.
It seems that I am not seeing that 302 and the Drafts API is handling that redirect, and only giving the 200 response to Drafts internal second request.
Would it be possible for a “no redirects please” flag to be added to HTTP.request? So that I can extract the cookies from the header and handle the redirect.