Compatibility issue with ALTCHA

  • Resolved Peter Duchnovsky

    (@pdux)


    11 months, 1 week ago

    Hello 🙂

    I am experiencing compatibility issue with ALTCHA, using Admin and Site Enhancements (ASE) Pro

    I have excluded altcha ASE scripts from minify
    /wp-content/plugins/admin-site-enhancements-pro/assets/premium/js/captcha/altcha/

    I have excluded API endpoint from caching for altcha callback
    *altcha*

    And yet, it fails to validate and (weirdly) it proceeds further without disallowing login.
    I have checked cache folder, it is not cached

    Once I disable this plugin, everything works as desired.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Peter Duchnovsky

    (@pdux)

    11 months, 1 week ago

    It seems it’s because of the browser cache headers set via htaccess.

    Thread Starter Peter Duchnovsky

    (@pdux)

    11 months, 1 week ago

    Found the cause, its:
    ExpiresDefault directive, with it disabled, everything works fine.

    Also, btw, im getting this error, even without commenting ExpiresDefault out, so there is something going on.

    Thread Starter Peter Duchnovsky

    (@pdux)

    11 months, 1 week ago

    Another solution is to simply set no-cache for API

    <IfModule mod_headers.c>
        <If "%{REQUEST_URI} =~ m#^/wp-json/#">
            Header set Cache-Control "no-store, no-cache, must-revalidate, max-age=0"
        </If>
    </IfModule>

    Maybe it would be benificial to let users choose whether they want to cache API as well.

    Plugin Support Damilare

    (@deabiodun)

    11 months, 1 week ago

    Hi @pdux!
    Glad to see that you’ve resolved this issue.
    Did you try adding /wp-json/* to the URLs to exclude from caching section at WPO > Cache > Advanced settings? Doing so should have resolved the issue with API caching.

    Let us know if there’s any other way we can assist you further.

    Regards.

    Thread Starter Peter Duchnovsky

    (@pdux)

    11 months, 1 week ago

    No that has no effect since, im assuming, the default rule for caching is being set via htaccess and wp-optimize does not create any htaccess rules overriding that.

    Also, you disable FileETag as well, might also lower chances of browser not caching api (but I tested and enabling them back doesn’t help)

    Plugin Support Damilare

    (@deabiodun)

    11 months ago

    Yes, we disable FileETag for more consistent caching results.
    Thanks for your input though. I’ll bring your submissions to the attention of our development team.

    Regards.

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

The topic ‘Compatibility issue with ALTCHA’ is closed to new replies.