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

Check if headers are empty and then flush and get the headers again #179

Merged
merged 1 commit into from Feb 3, 2017

Conversation

Projects
None yet
1 participant
@donnchawp
Contributor

donnchawp commented Feb 3, 2017

In #127 flush() was removed but a comment on apache_response_headers()
said that function may return an empty array, so I check for that here
and do a flush() before getting the headers again.

Check if headers are empty and then flush and get the headers again
In #127 flush() was removed but a comment on apache_response_headers()
said that function may return an empty array, so I check for that here
and do a flush() before getting the headers again.

@donnchawp donnchawp merged commit 02f4912 into master Feb 3, 2017

kraftbj pushed a commit that referenced this pull request Feb 9, 2017

donncha
* Github merge:
* Make sure $cache_path has a trailing slash (#77)
* Remove flush() (#127) but also check if headers are empty and flush and get headers again. (#179)
* Add fix for customizer (#161) and don't cache PUT AND DELETE requests (#178)
* Check for superglobals before using them. (#131)



git-svn-id: http://plugins.svn.wordpress.org/wp-super-cache/trunk@1588365 b8457f37-d9ea-0310-8a92-e5e31aec5664

@donnchawp donnchawp deleted the check_headers_and_maybe_flush branch Jul 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment