Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the cacheBuster key definable by setting an options #42

Open
frewillems opened this issue Mar 29, 2017 · 1 comment
Open

Make the cacheBuster key definable by setting an options #42

frewillems opened this issue Mar 29, 2017 · 1 comment

Comments

@frewillems
Copy link

HI guys,

I'm currently working in an environment where we have to specifically allow get parameters. We are behind Akamai and they ignore all not allowed params. We have a company wide standard for our cacheBuster keys, 'c'. So I was looking for an option to set the key, and I was surprised to see this is not possible.

What about changing options.cacheBuster so it can contain a string. So when this option is undefined, we default to 'z', when false we default to '' and when actually defined, we use the provided string.

@alvinlin123
Copy link
Member

Sounds like a good idea, feel free to submit a pull request or I can make it happen when I find some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants