Hot answers tagged 403
3
It's probably because Xenu is trying to pull up the page to verify the link is valid but Wikipedia is blocking it because it is an unauthorized bot. They probably are blocking a long list of crawlers and bots that are not related to search engines (i.e. link checkers, spammers, scrapers, etc).
3
Create an .htaccess file in the directory you wish to block, or your root HTML directory if you want this to affect your entire website. Place this code inside:
# Block includes if they have a .inc.php extension. Change
# that to match whatever extension you use for your includes.
<Files *.inc.php>
Order Deny,Allow
Deny from All
</Files>
# ...
3
My interpretation of that header is that the HTTP specification was not followed properly and a required field is missing or bad data is provided. For example a header is missing or invalid characters are used in the request, etc.
Some malformed request exam-ple:
GET /images/logo.png HTTP/2 # there is no HTTP 2
POTT /images/logo.png HTTP/1.1 # POTT should ...
2
I just looked at your page source, and (example) image: http://x3.keefermadness.com/lib/img/home/home-about.jpg loads perfectly fine by visiting that URL. Do you have a setting enabled for "disallow hotlinking" of images somewhere? It is possible that that could be causing the problem.
2
As you know Google will eventually remove pages which return server codes 404 Not Found and 410 Gone, however a 403 is a forbidden response from the server not an error.
Google will most likely continue checking the page and keep it in it's index in the event it becomes accessible. If you would like it to not be indexed set the meta noindex header tag
2
They get removed from the index. There is no official documentation from Google on this, but you can find plenty of cases where websites have been returning 403 by mistake and got deindexed.
Example case :
http://wordpress.org/support/topic/403-crawl-error-on-google-all-pages-have-been-removed-from-google-index
2
Found the error: Some silly module (don´t know wich one yet, added this code into my .htaccess file:
<Limit GET POST>
order deny,allow
allow from 24.232.0.0/16
allow from 66.60.0.0/18
allow from 129.214.0.0/16
allow from 140.191.0.0/16
allow from 157.92.0.0/16
allow from 161.190.0.0/16
allow from 163.10.0.0/16
allow from 167.252.0.0/16
[...]
allow ...
2
mickburkejnr is close, but not entirely right. The problem is not with DNS (it could be, but that's unlikely). The problem is that your web server isn't configured to respond to queries for your site without the "www" prefix with the appropriate site.
Keep in mind that "www" is just a normal subdomain. "google.com" is the root site, "www.google.com" is a ...
2
There is no way to forward the www > cdn without reaching the request on the main server since well they are linking to you.
My advice is not to 301 redirect but rather than just flat out 404, hopefully by doing so they will stop hot linking you.
While this has some traffic on your server it shouldn't be too much and you should consider upgrading your ...
2
Ouch, please avoid chmod 777, it's like having your door open with the key in the lock.
Error 13 is related to permission errors. In Linux, a folder needs a execute-bit to allow descending in it. So, make sure the permissions on /media/data and /media/data/jm is set to 755 OR 700 if the user running apache is the owner of the folders.
root is the god in ...
1
If you server is running Nginx+Passeneger , you can start your Ruby application in the following way:
cd /home/user/rails_apps/user; sudo -u user /usr/local/bin/ruby /usr/local/bin/passenger start -p 12045 -e production &
sudo -u user /usr/local/bin/ruby /usr/local/bin/passenger start -p 12421 -e production & - the command for running is screen
...
1
Unless you have your images on a sub-domain, there is no way to separate the traffic before it hits your web server.
One performance tip that might help you is to use both nginx and Apache on the same server. Have apache run on a non-standard port. Have nginx run on port 80 and have it reverse proxy requests to apache. The rewrite rule for the images can ...
1
On GWT, Health > Fetch as Google, and try to fetch one of the pages marked as "Access Denied". The result comes almost immediately.
It can be that your server is not well configured and for whatever reason it returned 403 when Google tried to crawl those pages. Fetching as Google will force the crawler to re-visit the page and if it returns 200 OK, the URL ...
1
Try this: (add +Indexes).
Options FollowSymLinks MultiViews +Indexes
What I suspect to be the issue, is that in your default Apache configuration somewhere it has a statement similar to the above, but for /var/www/ and therefore not the /home/.../ locations. If the above does NOT correct your issue, please let me know.
It doesn't usually matter the ...
1
You DNS record isn't set up to accept traffic to the server without the www. This is a simple A record, and all it will contain is either a blank space or "my0wnsite.com".
If you can't change the DNS records yourself, contact either your registrar or your hosting company and they will sort this out fairly quickly for you.
1
Will they be indexed:
403 Error – no, most search engines don't index error pages (assuming they're served with the correct HTTP status code)
Blank page – almost certainly not, assuming it is entirely blank (no <title>, nothing).
Page redirect – Generally only the destination of the redirect will be indexed (usually this is the intended result), but ...
1
IF you have links to the URLs that are returning a 403 error then you will leak whatever Page Rank that is being sent to that URL. Since Google is finding these 403 errors I assume something is linking to the URLs that are returning 403s.
However, unless it is your home page, it isn't going to be a huge SEO problem or loss of PR. Another good reason to ...
1
Are there any good tools that automatically monitor this background activity (specifically activity that throws errors on the web & db server) and proactively deal with these source(s) of mayhem?
"CloudFlare leverages the knowledge of a diverse community of websites to power a new type of security service. Online threats range from nuisances like ...
1
A few suggestions are to: 1) clear the users DNS cache, 2) disable any proxy settings, and 3) check their hosts file for any references to 127.0.0.1. It's possible that the user has a web server enabled on the local machine and is hitting that instead.
Just some thoughts. Hope they help.
Only top voted, non community-wiki answers of a minimum length are eligible
