• Resolved cantoute

    (@cantoute)


    Hi,

    Just noticed that wordfence emits a call from client (browser) to server of this type

    https://example.com/?wordfence_lh=1&hid=7A302CFF3D4FCDF3659569BXXXXXXXXX&r=0.374592099999999

    Would be nice if it returned a no-cache header (suspecting we don’t want proxies to cache this)

    The other problem I had is with a varnish setup to catch badly behaving backends that spots empty 200 response and restarts the query.
    Would be really nice if this returned something as dummy as {‘OK’}, at least not to have Content-Length: 0

    Hope this can be helpful

    (I really like your plugin, find it well coded, this is why I take the time to share my thougts)

    Have a nice day

    Antony

    • This topic was modified 6 years, 4 months ago by cantoute.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter cantoute

    (@cantoute)

    As it seams that managing headers within wordpress can be problematic, an other way to bypass proxy cache could be to add a &no-cache to the query string, would make it easy to spot.

    Thread Starter cantoute

    (@cantoute)

    sorry for typo, seems like &nocache would be more common

    Hi Antony,

    Thanks for your suggestion, I’ve logged this as a feature request to our team (internal reference number: FB7343), although I’m not sure if this can be seen in one of the plugin’s upcoming releases or not, but all suggestions are evaluated by our dev team and considered seriously.

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘suggestion for reverse proxy integration’ is closed to new replies.