Contao 4 - htaccess small issue

Code:

---

# Rewrite all other queries to the front controller.
  RewriteRule ^ %{ENV:BASE}/app.php [L]

---

Having above line in standard contao4 installation .htaccess file breaks the default behavior of a web server to serve index.html from a directory. Say for example, you have static html page named as index.html inside a directory "foo". With Contao 4 installation you can not see the page by calling "yourdomain.com/foo/" - error "ERR_TOO_MANY_REDIRECTS". It only works if your call "yourdomain.com/foo/index.html".

Is there any workaround? Not to mention you can add index.html at the end. But in my case, there are many such URLs already published.

This is the complete .htaccess of a Contao 4.4.33 installation:

Code:

---

<IfModule mod_headers.c>
    # Allow access from all domains for webfonts (see contao/core-bundle#528)
    <FilesMatch "\.(ttf|ttc|otf|eot|woff2?|font\.css)$">
        Header set Access-Control-Allow-Origin "*"
    </FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On

    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by Apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the start page because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    #  following RewriteCond (best solution)
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$1 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule ^ - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule ^ %{ENV:BASE}/app.php [L]
</IfModule>

<IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
        # When mod_rewrite is not available, we instruct a temporary redirect of
        # the start page to the front controller explicitly so that the website
        # and the generated links can still be used.
        RedirectMatch 302 ^/$ /app.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

---

Specifically, look at the following part:

Code:

---

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule ^ - [L]

---

If you have a file named index.html and you request that file via example.org/index.html, then it will be served by Apache.

If you want the file to be visible via example.org/ (i.e. without any additional request paths), then you would need your own directives.

Thanks for posting complete .htaccess.

Quote:

---

Originally Posted by Spooky

If you want the file to be visible via example.org/ (i.e. without any additional request paths), then you would need your own directives.

---

How? This is actually I wanted to know.

May be something like

Code:

---

RewriteRule ^$ %{ENV:BASE}/index.html [L]

---

after

Code:

---

RewriteRule ^(.*) - [E=BASE:%1]

---

No, not working with

Code:

---

RewriteRule ^$ %{ENV:BASE}/index.html [L]

---

as you pointed out after.

Code:

---

RewriteRule ^(.*) - [E=BASE:%1]

---

Url structure is like -> https://www.domain.com/files/path1/pathN/finalfolder/ and inside the "finalfolder", I've index.html

Oh, I thought you needed it for the root. Then you need a RewriteCond or RewriteRule, that excludes the whole files folder from the rewriting - or you add RewriteCond %{REQUEST_FILENAME} -d

Thanks, but I'm not able to solve it.