Support » Plugin: SG Optimizer » x-proxy-cache always MISS

  • Resolved guidotg

    (@guidotg)


    Hello,
    I’ve been trying to fix this issue for weeks now.
    SG caching is still not working and I always get x-proxy-cache: MISS.

    All I know for sure is, cache seems to works only if I deactivate Formidable Forms plugin (Lite version, not Pro. Both are required in order for Pro to work).
    So I open a ticket with Formidable but after many days of back and forth they ended up saying it’s impossible that their plugin sends headers that may prevent dynamic caching system from working.
    Also opened a few tickets with SiteGround, and honestly, it was frustrating having many different people responding to the same ticket each of them having different opinions.
    So I hired a pro developer to look into this but he was not able to figure out what the problem is, only saying there must be some misconfiguration in Nginx server (which I don’t believe).

    I’ve also opened a ticket here a couple of weeks ago and I was told “Something in your website keep sending Cache-Control: no-cache, must-revalidate, max-age=0 which disables our cache”.
    Now, is there a way to prove that these headers are sent by Formidable plugin, so that I can open another ticket with them? I sent them screenshots that shows x-proxy-cache: HIT when their Lite plugin is deactivated but they keep saying this is not possible. Really frustrating. I don’t know what else I can do.

    Any help or suggestion would be greatly appreciated!
    Thank you

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    Hey @guidotg

    You are correct. The Formidable User Tracking plugin starts a session on the init hook, which is called on every page load.

    When a session is started, the No-cache headers are sent to the server, which stops the caching of the page/resources.

    The session is started in the following method:
    maybe_start_session, which is called by compile_referer_session, which is hooked on the init hook:
    add_action( 'init', 'Frm_User_Tracking::compile_referer_session', 1 );

    Cheers,
    Stanimir

    Thread Starter guidotg

    (@guidotg)

    Hey Stanimir,
    I can’t thank you enough for this, you are a life-saver!
    Have been scratching my head for long time.
    Thank you again so much!!
    Guido

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.