Unable to rewrite multiple URL rewrite with same paramters - apache

Question

Need your expert help. I am trying to rewrite 2 url's in htaccess where both url's have same parameters. After rewriting url only 1st url rewrite is working. Can anybody help me on how to make both url rewrite work?
Here is my htaccess code code.
1st URL : http://www.example.com/quotaid.php?id=id/address
which i want to rewrite to
http://www.example.com/id/address
//1st URL rewrite
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/([a-zA-Z0-9]+|[0-9a-zA-Z]+)/?$
RewriteRule ^([a-zA-Z0-9]+|[0-9a-zA-Z]+)/(.*)$ quotaid.php?id=$1 [NC,L]
2nd URL : http://www.example.com/zipquota.php?zip=zip/address
which i want to rewrite to
http://www.example.com/zip/address
//2nd URL rewite in htaccess
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/([a-zA-Z0-9]+)?$
RewriteRule ^(.*)$ zipquota.php?zip=$1 [NC,L]
Only one url rewrite is working which comes first. If i move the 2nd url rewrite to top, then the 2nd url rewrite is working but the 1st url stops working. PLease help on how to manage both url rewrite working.

Answer 1

I assume this is what you are looking for:
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^/?([0-9]+)/(.+)$ /zipquota.php?zip=$1&address=$2 [NC,END]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^/?([0-9a-z]+)/(.+)$ /quotaid.php?id=$1&address=$2 [NC,END]
These are the internal rewritings applied by that, as specified by you in the comments to the question, though I dare say that the address argument makes zero sense and probably will get removed in future...:
https://example.org/91007/HOMES-FOR-Arcadia-CA => /zipquota.php?zip=91007&address=HOMES-FOR-Arcadia-CA
https://example.org/CV17057071/3677-Louise-Street-Lynwood-CA-90262 => /quotaid.php?id=CV17057071&address=3677-Louise-Street-Lynwood-CA-90262
Those rules should work in the http servers host configuration and likewise in dynamic configuration files (.htaccess). To be able to use them in a dynamic configuration file some preconditions have to be matched: the interpretation of such files has to be enabled in the http servers configuration (AllowOverride ...), the file has to be readable by the http server and it has to be placed inside the DOCUMENT_ROOT folder configured for that http host.
The zip based URLs are rewritten first, since they use a more specific pattern, purely number based. Then comes the more general rule for ids with alphanumeric patterns. The condition you originally had does not really make sense, I removed it.
Note: I also took the liberty to make those target paths absolute (leading slash) to make the setup more robust. That obviously requires those scripts to be located directly inside the DOCUMENT_ROOT folder. otherwise the paths have to be adjusted.
Warning: In case you get a http status 500 (internal server error), chances are that you operate a very old version of the apache http server. In that case you have to replace the END flag with the L flag. You can see a hint on that in your http servers error log file in that case. The L flag should work too, unless you have more rewriting rules that might create a conflict.
And a general hint: you should always prefer to place such rules inside the http servers host configuration instead of using dynamic configuration files (".htaccess"). Those files are notoriously error prone, hard to debug and they really slow down the server. They are only provided as a last option for situations where you do not have control over the host configuration (read: really cheap hosting service providers) or if you have an application that relies on writing its own rewrite rules (which is an obvious security nightmare).