[TASK] Do not set application context by default in htaccess 43/42943/2
authorHarry Glatz <glatz@analog.de>
Mon, 31 Aug 2015 13:40:09 +0000 (15:40 +0200)
committerAndreas Fernandez <a.fernandez@scripting-base.de>
Mon, 31 Aug 2015 13:54:17 +0000 (15:54 +0200)
Since the Production context is the default if no context is set
via environment variables, we do not forcefully set
the context in template .htaccess either.

This allows to set the context via webserver configuration
without the need to touch the lines in the .htaccess file.

Resolves: #69434
Releases: master, 6.2
Change-Id: I70915c51479c91c0db22c7637e46cb1c0fae2db4
Reviewed-on: http://review.typo3.org/42943
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>
_.htaccess

index 2e06138..577b834 100644 (file)
@@ -265,7 +265,7 @@ AddDefaultCharset utf-8
        #RewriteCond %{HTTP_HOST} ^staging\.example\.com$
        #RewriteRule .? - [E=TYPO3_CONTEXT:Production/Staging]
        #RewriteCond %{HTTP_HOST} ^www\.example\.com$
-       RewriteRule .? - [E=TYPO3_CONTEXT:Production]
+       #RewriteRule .? - [E=TYPO3_CONTEXT:Production]
 
        # Rule for versioned static files, configured through:
        # - $GLOBALS['TYPO3_CONF_VARS']['BE']['versionNumberInFilename']