# adding follow\_redirects option to the unarchive module

**URL:** <https://forum.ansible.com/t/adding-follow-redirects-option-to-the-unarchive-module/26394>\
**Category:** Ansible Developer\
**Created:** [December 29, 2017, 4:29pm UTC](https://forum.ansible.com/t/adding-follow-redirects-option-to-the-unarchive-module/26394 "2017-12-29T16:29:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tricker](https://avatars.discourse-cdn.com/v4/letter/t/d78d45/32.png) [@tricker](https://forum.ansible.com/u/tricker)\
**Post date:** [December 29, 2017, 4:29pm UTC](https://forum.ansible.com/t/adding-follow-redirects-option-to-the-unarchive-module/26394/1 "2017-12-29T16:29:02Z")

</div>

Does the community have any interest in adding the follow\_redirects option to the unarchive module? I’ve run into a situation where I could use such a thing.

It looks like it could be relatively straightforward to implement as the underlying module\_utils/urls.py fetch\_url function already implements it. _Just_ a matter of passing the option though.

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [January 2, 2018, 3:18pm UTC](https://forum.ansible.com/t/adding-follow-redirects-option-to-the-unarchive-module/26394/2 "2018-01-02T15:18:40Z")

</div>

We have previously decided that complex http scenarios with the unarchive module would not be added. Instead you should look to using the get\_url module to independently fetch the file, and then utilize unarchive with remote\_src=true.