-
Notifications
You must be signed in to change notification settings - Fork 215
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
Vimexx hosting compatibility #2803
Comments
@piotrbak Is there a way to know a website is hosed on Vimexx? |
@GeekPress After speaking with @piotrbak, I've sent them an email about this: https://secure.helpscout.net/conversation/1204722684/175580?folderId=377610 |
Thanks 🙏 |
Related ticket of a Vimexx customer: |
Related ticket https://secure.helpscout.net/conversation/1227894272/180833/ |
Testing account info here: https://secure.helpscout.net/conversation/1227675409/180792?folderId=377610#thread-3562847380 |
Related ticket - https://secure.helpscout.net/conversation/1377218868/226221 |
Related ticket: https://secure.helpscout.net/conversation/1520157492/265830/ The Vimexx-specific headers were set using: add_filter('rocket_varnish_purge_headers', 'filter_rocket_varnish_args' );
function filter_rocket_varnish_args( $headers ){
$headers[ 'X-Purge-ZXCS' ] = 'true';
$headers[ 'host-ZXCS' ] = $headers['host'];
return $headers;
} However, adding Vimexx's IPs using our helper plugin, didn't purge the cache.
add_filter( 'rocket_varnish_http_purge_scheme', function( $scheme ){
$scheme = 'https';
return $scheme;
});
add_filter( 'rocket_varnish_purge_url', function( $purge_url ) {
$purge_url = str_replace( '185.104.28.118', 'varnish3.zxcs.nl', $purge_url);
return $purge_url;
}); |
Vimexx hosting is using Varnish on their servers. In order to purge their cache, we need to add additional headers to our requests:
host-ZXCS:
X-Purge-ZXCS: true
Current state
Right now we can use the following snippet to make the compatibility:
http://snippi.com/s/21eii77
Ideal state
Make automatic detection and integration with this hosting provider.
Related tickets:
https://secure.helpscout.net/conversation/1194833523/172813
https://secure.helpscout.net/conversation/1155460964/162836/
Backlog Grooming (for WP Media dev team use only)
The text was updated successfully, but these errors were encountered: