404 hendler AO + 404 redirect homepage plugin

Ok, so i will of the option 404 in autoptimize and delete the handler.

Thank you, Frank 🙂
Appreciate this.

Frank, i hope you didn’t close this topic.
i tried now to reactive the 404 ao Hendler and off the plugin.
i server static files.

but I see in the handler you said:

* will have a “Errordocument:” directive to automatically do this.

in the htacsses.
no, i have inside the htacsses:
#ErrorDocument 404 /index.php?error=404

to activate that?
or you have another ErrorDocument i need to put?

the site i do the test is:
locksmithunit.cat

please if you can help me with that maybe i will use the hendler.
and about Nginx. i need to by pass the PHP AO hendler?

• This reply was modified 5 years, 2 months ago by Nadav Levi.

I try to do it with Nginx is a little problem to use it in Nginx.

but i can do it from apache.

Now in the FAQ you send, they say the handler adds an Error_document to htacsses.
but nothing is not added.

if you can give me the error_document for apache.
let’s see if it will work for us.

I did the static file option in auto optimize:
locksmithuni.cat

Let’s see if apache will do the job for us.

Ok, think i got it.
so you said is working.
the only dilemma i have is where to put the Nginx block ( i have already one block of css/js for all the folder himself. so need to add it without hurt the other one )

i know you not specialized in NGINX but I need you to check it for me just in case i not make
a mistake… 🙁

so in your FAQ:
location ~* /wp-content/cache/autoptimize/.*\.(js|css)$ {
try_files $uri $uri/ /wp-content/autoptimize_404_handler.php;
}

Now I have one like this:

location / {
    try_files $uri $uri/ @backend;
}

location @backend {
    include proxy_params_common;
    # === MICRO CACHING ===
    # Comment the following line to disable 1 second micro-caching for dynamic HTML content
    include proxy_params_dynamic;
}

# Enable low duration browser cache for static data files (TTL is 1 min)
location ~* \.(?:csv|json|xml|rss|atom)$ {
    include proxy_params_common;
    include proxy_params_static;
    expires 1m;
}

# Enable browser cache for CSS / JS (TTL is 30 days)
location ~* \.(?:css|js)$ {
    include proxy_params_common;
    include proxy_params_static;
    expires 365d;
}

# Enable browser cache for images (TTL is 60 days)
location ~* \.(?:ico|jpg|jpeg|gif|png|webp|mp3|mp4)$ {
    include proxy_params_common;
    include proxy_params_static;
    expires 365d;
}

# Enable browser cache for fonts & fix @font-face cross-domain restriction (TTL is 60 days)
location ~* \.(eot|ttf|otf|woff|woff2|svg|svgz)$ {
    include proxy_params_common;
    include proxy_params_static;
    expires 365d;
}

# Prevent logging of favicon and robot request errors
location = /favicon.ico {
    include proxy_params_common;
    include proxy_params_static;
    expires 60d;
    log_not_found off;
}

location = /robots.txt  {
    include proxy_params_common;
    include proxy_params_static;
    expires 1d;
    log_not_found off;
}

# Deny access to files like .htaccess or .htpasswd
location ~ /\.ht {
    deny all;
}

________________________________________________________

Now if i only know where to put your block exactly, it was perfect.
i think above mine CSS/JS bus i not sure.

in page speed when I put your above my CSS/js one of the scripts gone in the warning
(is actually good)

When I put him in the end next to the robots.txt location I still got one script more.
if you only recommended me where exactly put it is perfect,
this because we know is working.

Hey 🙂
is working without any block in Nginx.

I verified that.
I only think is better put ErrorDocument 404 in the .htacsses, just in case
nginx not serve the fallback.
( Nginx do a good job, but can make sure with apache as well )

what did you recommend?

ErrorDocument 404 /wp-content/autoptimize_404_handler.php?error=404
or
ErrorDocument 404 /index.php?error=404