Forum

Thread tagged as: Problem, Runway

403 issue on the index page

I found out I have an issue on the index page. With .htaccess I redirect my http to https, but as well as the Google-bot as my SEO software-bot, send back an 403 forbidden, but the page is still accessible.

When I add an index.php or index.html file inside my public_html this issue is resolved. But as I use Runway this is not an actual file.

On my other Runway installation I have another website and there it works just fine. Has anyone experienced this before? Or has anyone an idea how I can solve this in a normal way?
Kevin Hendriks

Kevin Hendriks 0 points

  • 3 years ago
Drew McLellan

Drew McLellan 2638 points
Perch Support

3 years ago

Why are you sending a 403?
Kevin Hendriks

Kevin Hendriks 0 points

3 years ago

It sends back an 403 error to me. I'm not sending it.
Drew McLellan

Drew McLellan 2638 points
Perch Support

3 years ago

What's in your .htaccess file?
Kevin Hendriks

Kevin Hendriks 0 points

3 years ago 
# Perch Runway
RewriteEngine On

RewriteCond %{HTTP_HOST} .
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

RewriteCond %{REQUEST_URI} !^/perch 
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule .* /perch/core/runway/start.php [L]

ExpiresActive On
ExpiresDefault A0
<FilesMatch “\.(gif|jpg|jpeg|png|swf)$”>
# 2 weeks
ExpiresDefault A1209600
Header append Cache-Control “public”
</FilesMatch>
<FilesMatch “\.(xml|txt|html)$”>
# 2 hours
ExpiresDefault A7200
Header append Cache-Control “proxy-revalidate”
</FilesMatch>
<FilesMatch “\.(js|css)$”>
# 3 days
ExpiresDefault A259200
Header append Cache-Control “proxy-revalidate”
</FilesMatch>
Drew McLellan

Drew McLellan 2638 points
Perch Support

3 years ago

This says "requested file is not a directory"

RewriteCond %{REQUEST_FILENAME} !-d

But it is a directory. So you probably don't need that.