Panel problem because of .htaccess

Hello nice people,

beside Kirby I use another tool with an admin area and therefore I need the following lines in my .htacess file:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule api/(.) zipcode/$1 [L]
RewriteRule jump/(.
) zipcode/$1 [L]

Unfortunately I can’t log in to the Kirby Panel then.
I get the following error: The JSON response could not be parsed

Here is my complete .htaccess file:

# Kirby .htaccess
# revision 2020-06-15

# rewrite rules
<IfModule mod_rewrite.c>

# enable awesome urls. i.e.:
RewriteEngine on

# make sure to set the RewriteBase correctly
# if you are running the site in a subfolder;
# otherwise links or the entire site will break.
# If your homepage is,
# set the RewriteBase to:
# RewriteBase /mysite

# In some environments it's necessary to
# set the RewriteBase to:
RewriteBase /

RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTP_HOST} ^(?:www\.)?(.+)$ [NC]
RewriteRule ^ https://www.%1%{REQUEST_URI} [L,NE,R=301]

# the following 4 lines do the problem
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule api/(.*) postleitzahl/$1 [L]
RewriteRule jump/(.*) postleitzahl/$1 [L]

# block files and folders beginning with a dot, such as .git
# except for the .well-known folder, which is used for Let's Encrypt and security.txt
RewriteRule (^|/)\.(?!well-known\/) index.php [L]

# block all files in the content folder from being accessed directly
RewriteRule ^content/(.*) index.php [L]

# block all files in the site folder from being accessed directly
RewriteRule ^site/(.*) index.php [L]

# block direct access to Kirby and the Panel sources
RewriteRule ^kirby/(.*) index.php [L]

# make site links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php [L]


# pass the Authorization header to PHP
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

# compress text file responses
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript

I hope someone can help me with this :slight_smile:

I would advice to not mix up different websites/tools/apps in one folder. Set up different virtual hosts or us subfolders if virtual hosts are not feasible.

Oh yes, the tool is in another folder. The .htaccess is something like an jump in to the postleitzahl folder. In Kirby 2 it worked in the .htaccess file.

Then, I would use only the rule with jump into the postleitzahl folder. In the kirby folder you can use the original .htaccess file for kirby and in the postleitzahl folder you would use an .htaccess file with only the api rewrite (if it is necessary at all in such a setup).