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
{{ message }}
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
and all pages are in the form of http://example.com/controller/action/params/, how should I update the rewrite rules for db-to-api or is it best just to run it along side of the application instead of trying to integrate with? Thanks.
The text was updated successfully, but these errors were encountered:
I use rewrite rules and had to get around the same problem. I found it easiest to add an "api" directory to the root of my application and have the rewrite rules ignore that directory completely. That way the db-to-api can use its own rewrite rules separate from my own application. The rule looks like this:
RewriteRule ^(api) - [L]
Hope I'm understanding the question correctly and that this helps.
Thanks,
ry
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am very weak in the department of rewrite rules. So, if my current rewrite rule is this:
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule ^(.+)$ index.php?url=$1 [QSA,L]
and all pages are in the form of http://example.com/controller/action/params/, how should I update the rewrite rules for db-to-api or is it best just to run it along side of the application instead of trying to integrate with? Thanks.
The text was updated successfully, but these errors were encountered: