Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter acornils

    (@acornils)

    AWS Cloudfront and S3 are configured correctly and content is be cached and served by the CDN. Issue as explained above is under this setup cache control headers are being set for max-age or expires. This due do to the interaction on AWS between Cloudfront and the S3 origin the requires this options to be set on the S3 object when it is put into the S3 bucket by the plugin. The plugin has not been programed insert these metadata values when it posts the content to the S3 in my opinion should be because in it’s current state it is preventing content from being cached by web browsers.

    Thread Starter acornils

    (@acornils)

    Further update on this issue it seems to be related to the default values in the Ignored query stems:

    I have the following defaults

    gdsr_
    wp_rg_
    _wp_session_

    If either wp_rg_ or _wp_session_ is in the list the plugin will not save the settings if I remove them and only have gdsr_ or nothing at all the settings save just fine.

Viewing 2 replies - 1 through 2 (of 2 total)