You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear all I recognized an issue with v1.7.1.6 that the password protection is not working in case I have context specified for a virtual location (when it does not exist on the filesystem) and rewriting rules have been applied.
Example
specif a static context with a virtual URI e.g. "/backend/"
specify rewriting rule to map any request to "index.php" in this context
specify for this context a password protection through realm
result: No password protection will appear but the rewriting get applied
I also tried to make use of other contexts like "Litespeed SAPI" with "/backend/" but this is not usable because I can not specify any rewriting rules at this context.
So how can I achieve to have for a virtual location a password protection enabled for which then later the rewriting rules can be applied / used?
According to my understanding and comparison to Apache, I think the password protection has first to be evaluated and then afterwards the rewriting rules.
The text was updated successfully, but these errors were encountered:
egloffmark
changed the title
Combination of Password Protection and Reqriting Rules not possible
Combination of Password Protection and Rewriting Rules not possible
Nov 28, 2022
Dear all I recognized an issue with v1.7.1.6 that the password protection is not working in case I have context specified for a virtual location (when it does not exist on the filesystem) and rewriting rules have been applied.
Example
result: No password protection will appear but the rewriting get applied
I also tried to make use of other contexts like "Litespeed SAPI" with "/backend/" but this is not usable because I can not specify any rewriting rules at this context.
So how can I achieve to have for a virtual location a password protection enabled for which then later the rewriting rules can be applied / used?
According to my understanding and comparison to Apache, I think the password protection has first to be evaluated and then afterwards the rewriting rules.
The text was updated successfully, but these errors were encountered: