# How to add a browser cache busting mechanism to WorkflowGen

**URL:** <https://discuss.workflowgen.com/t/how-to-add-a-browser-cache-busting-mechanism-to-workflowgen/720>\
**Category:** Installation\
**Created:** [March 6, 2017, 8:08pm UTC](https://discuss.workflowgen.com/t/how-to-add-a-browser-cache-busting-mechanism-to-workflowgen/720 "2017-03-06T20:08:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\
**Post date:** [March 6, 2017, 8:08pm UTC](https://discuss.workflowgen.com/t/how-to-add-a-browser-cache-busting-mechanism-to-workflowgen/720/1 "2017-03-06T20:08:11Z")

</div>

Adding a cache busting mechanism to WorkflowGen is useful because it eliminates the need to clear the browser cache after upgrades to see the most recent updates. Developers can make these updates available to end-users immediately without having to clear their caches.

**Note: WorkflowGen v8 has already some built-in cache busting capabilities. If some files are still loaded from your browser cache, you can use the solution below for those specific files.**

To add a cache busting mechanism:

1. Download and install [URL Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite) on the WorkflowGen IIS web server.

2. Create a new web.config file with the following contents and add it to the `wfgen` folder’s parent folder (e.g. \inetpub\wwroot), replacing the version number in the `value` attribute of the `<action>` tag (`v=X.X.X`) with your version number of WorkflowGen (this example uses `v=7.1.0` for version 7.1.0), or you can use your own business versioning rules.  
  
**Notes**  

Reference to the original solution: [GitHub - JeevanJames/CacheBustingWithIISRewrite: Demonstrates cache busting with IIS rewrite outbound rules](https://github.com/JeevanJames/CacheBustingWithIISRewrite)