Closed (fixed)
Project:
Acquia Purge
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Sep 2013 at 20:16 UTC
Updated:
25 Aug 2014 at 21:12 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
barrett commentedComment #2
barrett commentedThere's likely a more efficient means of doing this. It would also be nice to have a configuration option to tell the module if it should clear http, https, or both. For the moment, the patch at least solves the problem.
Comment #3
nielsvm commentedHi Barret,
Your patch might work for your scenario but it needs further groundwork to get it really done well. I have finished a major refactor of the HTTP requesting internals in which I kept https purging fully in mind. If you are interested short-term let me know, else you can assume https support to end up as experimental feature soon!
Niels
Comment #4
barrett commentedThanks, Niels. We're definitely interested in this feature in the near-term. I'll see what I can do about re-rolling the patch against the revisions you've made to the module.
Thanks,
Barrett
Comment #5
nielsvm commented@barrett, you are welcome!
I have worked on refactoring the underlying HTTP logic to - primarily improve performance and decrease the burden put on the queue api - support HTTPS support in the future. Although adding HTTPS support with GUI interface and everything isn't the highest priority right now, it should already work with a one-line hack.
Please upgrade to version *7.x-1.0-alpha2* which gives you many performance improvements already, then there is the patch attached to this comment. This should effectively give you https support during purging.
Please test carefully as purging happens 'atomic', which means that one single request failing will result in your full queues filling up. You can track everything happening in Drupal's standard logging system, errors are flagged as such.
Looking forward to your feedback,
Niels
Comment #6
anavarre@Barrett: have you been able to test this?
Comment #7
nielsvm commentedThis will land in Acquia Purge one day but due the riskiness our current focus lies on getting a stable and working module out. The patch works for those in the meanwhile requiring SSL purging and I would love to see feedback on it. Again, all underpinnings to SSL purging are designed in but the last 1% has been removed: until I'm absolutely certain its safe to release.
Comment #8
alexku commentedAttaching a modified patch which makes https support optional and configurable in settings.php. Also it allows optionally skipping ssl verification in curl. Otherwise purge requests fail if ssl certificate is not valid.
To enable https purging and ssl verification skipping add this to settings.php:
Comment #9
jaydub commentedWe just ran into this issue as well as we just deployed HTTPS across our entire site on Acquia yesterday. We were not getting varnish PURGEs to do their thing and applying the patch and settings.php change resulted in successful PURGE to https bucket on Varnish.
Comment #10
technikh commentedThe patch worked great for us. Don't forget to add this code to settings.php
Comment #11
dstolA small whitespace fix.
Comment #12
nielsvm commentedGentlemen,
I've got good news for all of you for the upcoming release 7.x-1.0:
The implementation is different than the patches posted here above and in my opinion safer as well. Letting people mess directly with the protocol schemes array feels wrong to me and could open a can of worms if someone mistypes something there.
So, I'm closing this ticket finally as fixed, as its soon available to all of you. Testers on the 7.x-1.x branch are welcome in the meanwhile to reopen the ticket if anything's found, but I don't expect so.
Niels