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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Add Referrer-Policy HTTP Header to Whitelist #892

Open
raamdev opened this issue May 26, 2017 · 0 comments
Open

Feature Request: Add Referrer-Policy HTTP Header to Whitelist #892

raamdev opened this issue May 26, 2017 · 0 comments
Assignees
@raamdev
Labels
enhancement
Milestone
Next Release

Comments

@raamdev
Copy link
Contributor

raamdev commented May 26, 2017

@jaswrks writes...

Regarding Referrer-Policy. I don't see any reason we can't support this header. It's just not in our existing whitelist. We should probably add it in. I have never used that before myself and browser support appears to be sparse, but it seems harmless. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

Here's the existing Comet Cache HTTP Header Whitelist as of v170220: https://github.com/websharks/comet-cache-pro/blob/170220/src/includes/traits/Shared/HttpUtils.php#L67-L112

Requested here: https://wordpress.org/support/topic/gzip-in-cpanel/#post-9168722
@raamdev raamdev added this to the Next Release milestone May 26, 2017
raamdev added a commit to wpsharks/comet-cache-pro that referenced this issue May 26, 2017
@raamdev
Preparing pull request. See: wpsharks/comet-cache#892
60f7dd8
@raamdev raamdev mentioned this issue May 26, 2017
Merged
raamdev added a commit to wpsharks/comet-cache-pro that referenced this issue May 26, 2017
@raamdev
Add Referrer-Policy to cachable HTTP headers whitelist
af5fc6f 
See wpsharks/comet-cache#892
raamdev added a commit to wpsharks/comet-cache-pro that referenced this issue May 26, 2017
@raamdev
Add changelog entry for wpsharks/comet-cache#892
c8f2e28
raamdev added a commit to wpsharks/comet-cache-pro that referenced this issue May 27, 2017
@raamdev
Allow cachable HTTP headers list to be filtered
9c27afa 
See wpsharks/comet-cache#892
@raamdev raamdev self-assigned this May 29, 2017
raamdev added a commit that referenced this issue Aug 8, 2017
@raamdev
Phing release of v170808-RC with the following changes:
39589da 
- **New Feature: Memcached / RAM** (Pro): Comet Cache Pro now includes support for Memcached / AWS ElastiCache to serve the cache directly from RAM. This allows for a faster cache delivery than what is possible when serving the cache via disk. Memcached / AWS ElastiCache can be configured from **Dashboard → Comet Cache Pro → Plugin Options → RAM / Memcached**. See [Issue #47](#47)
- **Enhancement**: Added `Referrer-Policy` to whitelist for cachable HTTP headers. See [Issue #892](#892).
- **Bug Fix** (Pro): The Cache Statistics feature was broken when the PHP `disk_total_space()` and/or `disk_free_space()` functions were disabled by the PHP configuration. Comet Cache now handles this scenario gracefully by hiding disk-related stats when those functions are not allowed. See [Issue #775](#775)
- **Bug Fix** (Pro): The HTML Compressor was returning an empty string upon encountering an invalid UTF-8 sequence. See [Issue #871](#871) reported by a Comet Cache user.
- **Compatibility** (Pro): Many improvements to the Pro software update system, including changes to the API Endpoints and the Proxy Fallback endpoint. See [Issue #879](#879) and [Issue #315](wpsharks/comet-cache-pro#315) for full details.
- **Compatibility**: Fixed a WooCommerce compatibility issue that was generating a "Notice: id was called incorrectly. Product properties should not be accessed directly." Props @vestaxpdx. See [Issue #896](#896).
@raamdev raamdev mentioned this issue Aug 8, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raamdev raamdev

Labels
enhancement
Projects
None yet
Milestone
Next Release
Development

No branches or pull requests
1 participant
@raamdev