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

VOTE: Multi Domain Support #5

Open
zanderwar opened this issue Nov 24, 2016 · 3 comments
Open

VOTE: Multi Domain Support #5

zanderwar opened this issue Nov 24, 2016 · 3 comments
Labels

Comments

@zanderwar
Copy link
Contributor

In some situations (where the "why" is definitely opinionated) people have multiple domains that access the same content e.g

  • mycooldomain.com - MAIN SITE
  • mycooldomain.net - MASK FOR MAIN SITE
  • mycooldomain.org - MASK FOR MAIN SITE

This module currently only supports the domain name it has been accessed from, that means if you access the administration panel via mycooldomain.com then only cache for the .com variant will be dynamically purged by this module.

Whilst you would think that in this situation, if you were to only purge the .com then the .net and .org will also reflect the purge as these domains only mask the original. Sadly that's not how CloudFlare works as it strictly caches the URL as a whole.

This issue is a poll to see if it would even be worth adding support for the above scenario where this module would also purge cache for all of your URL variants.

Please up vote one of the below comments

@zanderwar
Copy link
Contributor Author

Yes, I or my client has a similar scenario and adding this feature would help relieve a lot of stress for my client and/or myself

@zanderwar
Copy link
Contributor Author

No, neither I or my client would benefit from this feature

@zanderwar
Copy link
Contributor Author

zanderwar commented Dec 25, 2016

Given the above references, I believe there may be a thirdparty, multi-domain extension in the pipeline for this module which would be exceptional in the fact that it doesn't have to be implemented within the base code itself

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

No branches or pull requests

1 participant