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

Devel #897

Merged
merged 23 commits into from
Aug 27, 2015
Merged

Devel #897

merged 23 commits into from
Aug 27, 2015

Conversation

miguelbalparda
Copy link
Contributor

No description provided.

jeroenvermeulen and others added 23 commits July 9, 2015 21:57
The config setting [web/unsecure/base_url] can be https://... but ESI can never be HTTPS.
Varnish 3 will treat HTTPS URLs as relative, leading to a 404 in Magento, leading to recursive ESI includes.
Explicit cache bypass for progress sections.
Fix for viewed/compared blocks #801, #803
Varnish 4 Support - based off PR #541
Improved ESI Ajax: load async + fixed jQuery fallback.
When there were no messages, but there was HTML for the ESI Ajax container, it was thrown. When that happened, there was no ESI container on that page, so messages would never work on that cached page.
Pull request #825 broke the ESI messages. This commit fixes it.
miguelbalparda added a commit that referenced this pull request Aug 27, 2015
@miguelbalparda miguelbalparda merged commit 04bd33e into master Aug 27, 2015
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

Successfully merging this pull request may close these issues.

4 participants