403 forbidden error website

[MaartenvandenBos]

Hi Mozzers,

I got a question about new website from a new costumer http://www.eindexamensite.nl/.

There is a 403 forbidden error on it, and I can't find what the problem is.

I have checked on: http://gsitecrawler.com/tools/Server-Status.aspx
result:
URL=http://www.eindexamensite.nl/ **Result code: 403 (Forbidden / Forbidden)**

When I delete the .htaccess from the server there is a 200 OK :-). So it is in the .htaccess.

.htaccess code: ErrorDocument 404 /error.html

RewriteEngine On
RewriteRule ^home$ / [L]
RewriteRule ^typo3$ - [L]
RewriteRule ^typo3/.$ - [L]
RewriteRule ^uploads/.$ - [L]
RewriteRule ^fileadmin/.$ - [L]
RewriteRule ^typo3conf/.$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule .* index.php

Start rewrites for Static file caching

RewriteRule ^(typo3|typo3temp|typo3conf|t3lib|tslib|fileadmin|uploads|screens|showpic.php)/ - [L]
RewriteRule ^home$ / [L]

Don't pull *.xml, *.css etc. from the cache

RewriteCond %{REQUEST_FILENAME} !^..xml$
RewriteCond %{REQUEST_FILENAME} !^..css$
RewriteCond %{REQUEST_FILENAME} !^.*.php$

Check for Ctrl Shift reload

RewriteCond %{HTTP:Pragma} !no-cache
RewriteCond %{HTTP:Cache-Control} !no-cache

NO backend user is logged in.

RewriteCond %{HTTP_COOKIE} !be_typo_user [NC]

NO frontend user is logged in.

RewriteCond %{HTTP_COOKIE} !nc_staticfilecache [NC]

We only redirect GET requests

RewriteCond %{REQUEST_METHOD} GET

We only redirect URI's without query strings

RewriteCond %{QUERY_STRING} ^$

We only redirect if a cache file actually exists

RewriteCond %{DOCUMENT_ROOT}/typo3temp/tx_ncstaticfilecache/%{HTTP_HOST}/%{REQUEST_URI}/index.html -f
RewriteRule .* typo3temp/tx_ncstaticfilecache/%{HTTP_HOST}/%{REQUEST_URI}/index.html [L]

End static file caching

DirectoryIndex index.html

CMS is typo3.

any ideas?

Thanks!
Maarten

[jenallen]

Hi everyone,

I know this thread hasn't been active for a while but i'm looking for an answer relating to a similar issue. Our infrastructure team had issues a few weeks ago and were routing bot traffic to a slave server. This obviously flagged up 403 errors in webmaster tools.

Having removed the traffic diversion our site hasn't been indexed in the three weeks since serving Googlebot with a 403 response. Does anyone have experience of Google delaying reindexing of a site after experiencing a 403 response?

Thanks

[MaartenvandenBos]

Hi Alan,

Ok we start cutting the htaccess. I'll keep you posted.

Thanks!

[MaartenvandenBos]

Thanks Anthony!

That's the strange thing, website is working only there is still a 403.

We will check chmod status.

[loopyal]

Hello Maarten

Those RewriteCond entries are cumulative and it looks like there are missing commands.

Who edited that file last, and what did they change?

The way conditionals work is you set a condition, Then you add a command, then a line break You can add more than one condition and it acts as AND

This page has what look like too many conditions and not enough commands -but it could be ok

Try adding a blank line between the rule entries and the Cond entries (but not between the Cond and the Rule entries)

Here is what to do to test anything like this: Save a copy of the .htaccess Then start editing it Delete everything below ##Start rewrites See if that fixes it. If not, the problem is above or if that fixes it, the problem is below Keep cutting the file in half or adding half until you discover the problem line

It is harder with all those conditionals, I suspect it is the lower block that is the problem

So remove those Cond entries from the bottom up

[Anthony_NorthSEO]

Follow up:

I'm not seeing any errors when visiting the site (http://www.eindexamensite.nl/). It seems to be working perfectly. Could it be something client-side w/ your caching or system time?

[Anthony_NorthSEO]

Hi Maarten,

I'm not extremely familiar .htaccess or the typo3 CMS, but it could be the issue is simply a result of misconfigured file permissions for a specific directory or path.

I'd check the permissions on all of the paths that are affected by the .htaccess and make sure they're readable and executable (7,5,5).

This could explain why you get the 200 status w/o the .htaccess but the 403 error with it.

Good luck!