# Download link - Content Disposition - file save prompt

**URL:** <https://meta.discourse.org/t/download-link-content-disposition-file-save-prompt/25228>\
**Category:** Bug\
**Created:** [2015 年2 月 13 日 21:36 UTC](https://meta.discourse.org/t/download-link-content-disposition-file-save-prompt/25228 "2015-02-13T21:36:23Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

作者： ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
发布日期： [2015 年2 月 17 日 22:25 UTC](https://meta.discourse.org/t/download-link-content-disposition-file-save-prompt/25228/14 "2015-02-17T22:25:34Z")

</div>

I can confirm that a post from “Sep 12, 2014” fails to download as expected and a post from today works as expected on my instance.

Rebaking the individual (previously failing) post fixes the download link for all images in the post.

Looks like it was added here (Oct 15, 2014):  
[https://github.com/discourse/discourse/commit/31e9cafe0e053d04fce249a4059bc27ed0772c03](https://github.com/discourse/discourse/commit/31e9cafe0e053d04fce249a4059bc27ed0772c03)

So in-terms of rebaking (if you do confirm):

- Clear instructions to rebake perhaps should be added for the point version upgrade it effects?
- Rebake all button in the backend (with confirmation).
- Handling future required rebakes - possible way of flagging upgrades / updates as requiring rebaking posts.

Rebake impact question - I’ve never done a rebake only the baking that was done automatically on forum import.

The baking process at the time of import actually took ~7 days - rebaking worries me as to it’s impact on the forum…  
… it continuing to be usable and backups not causing an issue when running for multiple days.

---

_[View the full topic](https://meta.discourse.org/t/download-link-content-disposition-file-save-prompt/25228)._