Hello!
First of all thanks for doing good job! And also sorry for my English.

I use SecurePages. Some parts of site are https only, default is http, and logged in users are only on https.

I installed HTTPRL and checked "Handle drupal_http_request", and it broked it, so I unchecked it back.

Then I tried to use it with AdvAgg. All was fine. But if you flush advagg cache, and then go to https version of page - you will see insecure content warning and that content in at least in chrome will not load at all.
But. If I log in, then https will be turned on for ALL pages, and it will load all advagg content. After if you logout and go to https version of page, all will be fine again and will work. After flushing cache I need again to log in to fix it.

I think it caches https version in different way? It happens only with httprl turned on in advagg config.

This is my first bug report :)

Need I to use httprl? It will speed up only first time, yeah?

And by the way, two questions:
1. I have Bundler On, Preprocess all css, and CSS files count is set to 4. Also I use CSS injector. But all pages have about 7 advagg css files. Why?
2. If I use CDN module, need I turn on AdvAgg JS & CSS CDN modules? Or it is only for Google CDN?

CommentFileSizeAuthor
#2 advagg-2025919-2-fix-https.patch3.25 KBmikeytown2
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeytown2’s picture

Looks like the source for this is coming from my implementation of drupal_build_css_cache(); advagg_load_css_stylesheet(). Will see what is needed to do in order to get this working correctly :)

mikeytown2’s picture

Status: Active » Needs review
FileSize
3.25 KB

Mind testing this patch to see if this fixes it?

mikeytown2’s picture

Status: Needs review » Fixed

#2 has been committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

agittins’s picture

I'm seeing very similar (i think identical) behaviour in Drupal 6 as well. I updated to advagg-6.x-1.x-dev from 2013-Sep-30 but have still seen it pop up a few times. Is it likely the same issue or do I need to dig deeper?

mikeytown2’s picture

@agittins
Could you create a new issue for 6.x? It could be the same issue.

agittins’s picture

Cool, done. Bug report for 6.x versions: https://drupal.org/node/2137085