Please add an option to HTTP.request() to not follow redirects and add a headers property to HTTPResponse

Feature Requests
1

Invoking HTTP.request() with a method of “HEAD” does work, but only having access to statusCode is half of the picture of that situation.

2 Likes
2

I know this is an old feature request, but I’d like to second it.

My specific use case is a script that will take a URL input, fetch it, follow any redirects, and tell the user what the “final” URL was. The current behavior of always silently following redirects means that (1) even though Drafts knows the final URL, my script doesn’t, and (2) I can’t handle the redirects manually because my script never sees a 30x response itself.

3

Keep an eye on the release notes. This will be in the v37 release, exposed as a followRedirects boolean property on the HTTP object.

4

Awesome, thank you so much! :tada: