404-error

404 Error while accessing the font files

Please use short path file url rather then absolute path. So code is like: @font-face{ /* for IE */ font-family:FontFamily; src:url(Font.eot); } @font-face { /* for non-IE */ font-family:FontFamily; src:url(http://) format(“No-IE-404”),url(Font.ttf) format(“truetype”); } Make sure that readable web has released it’s first @font-face related software utility for creating natively compressed EOT files quickly and easily. … Read more

: Failed to load resource

I see a few errors in your code: Your first line: <html lang=”<?php language_attributes(); ?>” dir=”ltr”> should actually be: <html <?php language_attributes();?> dir=”ltr”> (notice that you dont need to add lang=. The function does that by itself. That will likely fix the problem) You didn’t add the ; to 2 of your lines in the … Read more

WP Rest API not working

First you’ve to Check if the WordPress REST API is enabled or not The best way to check is to visit this URL: https://yoursite.com/wp-json. If you see some JSON response, REST API is enabled. If it’s showing some error page or returns to home page, REST API is not enabled. Then we’ve to enable it … Read more

Deny access to a path (give 403 or 404 response)

# this give internal server error throughout site: <Files ~ “/users/”> Header set X-Robots-Tag “noindex, nofollow” </FilesMatch> This would give an “internal server error” (500 response) because you’ve used </FilesMatch> to close the <Files> section. It should be </Files>. But as you suggested, this won’t work anyway, as the <Files> directive matches real files only, … Read more

Site searches by Python for non-existent assets

What are the python searches? Are they like bad bots? Most probably just “bad bots” searching for potential vulnerabilities. How do I block or prevent them? Well, you are already serving a 404 by the sounds of it, so it’s really a non-issue. However, you can prevent the request from going through WordPress by blocking … Read more

+ More