Tag Info

Hot answers tagged

6

When I try to get a particular image on a remote domain via JavaScript I get a 403 error. Likely answer: The site in question has protection against "leeching" / hotlinking. i.e. It checks to see what host is requesting the file before serving it. If the request comes from an unrecognised website, they throw a 403 Forbidden error. If you take a look ...


5

Once Google Webmaster Tools reports 404 errors on your website, you have to fix the issue on the site, then you need to mark these errors as fixed in Google Webmaster Tools. Then if this error appears again on your site, Google Webmaster Tools will report it again, otherwise it's fixed.


4

This is probably a silly question, but did you restart your web server process after modifying httpd.conf? Sometimes I forget to do that...


4

It could be generated by a proxy server between the client and your server. Check the error message.


3

Found the error: Some silly module (don´t know which 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 ...


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

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 ...


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

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

I've been able to reset a lot of my site's values using appcmd, but I had to dig into specific configurations I wanted to change, which I'll describe a bit below. I know for sure that this works with IIS 7, but I'm not 100% certain whether it passed on to 7.5 so YMMV. appcmd isn't in my cmd path on any of my installations (though these machines are 2k8sp2) ...


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

You want to use the ErrorDocument rule. Using your example, it might look something like this: <IfModule mod_rewrite.c> RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?/$1 [L] </IfModule> ErrorDocument 403 index.php


2

The site appears to be checking the referrer field. curl -I http://mysticstars.net/gifs/star_bul.gif -e "*" HTTP/1.1 403 Forbidden Date: Wed, 25 Jun 2014 15:45:40 GMT Server: Apache/2.2.27 Accept-Ranges: bytes Vary: Accept-Encoding Content-Length: 1007 Content-Type: text/html curl -I http://mysticstars.net/gifs/star_bul.gif -e "http://mysticstars.net" ...


1

A good response might be HTTP 401 Not Authorized, as I presume that the site admin has the right credentials to view the page whilst no-one else has. The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the ...


1

Consider 404. There's no really right or wrong to your question since both error types you have listed with do the job but ideally if you want things operating the correct way then ideally your CMS should be not publishing the articles at all until you review the articles and click publish.... So the right message should be a simple '404' since the article ...


1

I'd guess you have .htaccess which uses mod_rewrite, and does not like your new subdomain for some reason. (If you had published your real URL, it might provide more info for debugging...)


1

Check the permissions for /home/username/rails-live/rails-app/public. Make sure the user running Nginx has read and execute permissions.


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

I would speak to your hosting provider, it sounds like maybe something they did on a server or network level. If they aren't helpful with it you could maybe speak to others with the same host to see if they had similar problems around the same time.


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

A 403 response doesn't really tell Google to stop trying to index this page. It's the server refusing the request. Google will probably continue trying to access these pages as it's not a 404. As John said it won't affect your rankings.


1

This won't affect your rankings. That error message will tell Google to stop crawling those pages and that's it.



Only top voted, non community-wiki answers of a minimum length are eligible