multiview | Spawn multiple processes and channel their outputs | Command Line Interface library

The resolution: Make sure you haven't left the same .htaccess file in the actual directory you are trying to rewrite. In this case, api/. Removing the errant .htaccess file and rebooting apache resolved the issue.

You may use it like this:

You actually have 2 problems here...

1. MultiViews (part of mod_negotiation) is enabled and it's this that is serving products.php.
2. Your RewriteRule pattern is incorrect and won't match the requested URL.

The "problem" is that you appear to be using relative URL-paths to your static resources (CSS, JS and images). So this is a client-side URL resolution issue. You should be using root-relative (starting with a slash) or absolute (with scheme + hostname) URLs to your assets so they can be located regardless of URL-path depth. (Note that any requests that your JS makes, eg. AJAX, should also be root-relative or absolute.)

The problem is not so much with .htaccess, but when you change the URL from /post.php?page=page_slug to /post/page_slug then any client-side relative URLs are going to resolve relative to /post/, not / (the document root) as before.

The request for the JS (and CSS) files result in a 404, so the 404 HTML error document is most probably being parsed as JS and failing (ie. "Uncaught SyntaxError: Unexpected token: '<'" - due to a or opening tag).

A possible workaround (to avoid changing your URLs) is to use a base HTML element in the head section to indicate what any relative URLs should be resolved relative to, overriding the URL of the current document. However, this has some additional caveats if you are using in-page anchors of the form href="#element" - since they will now be resolved relative to the document stated in the base element and not the current document.

See also my answer to the following question on the Webmasters stack that goes into more detail on this:

• https://webmasters.stackexchange.com/questions/86450/htaccess-rewrite-url-leads-to-missing-css

but after completing my survet php redirects to www.example.com/survey_thank_you.php?survey_id=1

You need to "correct" the URL that PHP is redirecting you to after the survey. If the desired URL is /thank_you (or /Thank_you?) then PHP should be redirecting to that URL.

You then use mod_rewrite in .htaccess to internally rewrite /thank_you back into the URL that your application understands. ie. /survey_thank_you.php?survey_id=1. However, therein lies another problem, where does the 1 (survey_id) come from in the query string? Presumably you don't want to hardcode this? So this would need to passed in the requested URL. eg. /1/thank_you or perhaps /thank_you/1?

However, is this really necessary? The resulting "thank you" page is not a page that should be indexed or a page that is normally navigated to by the user, so implementing a user-friendly URL here doesn't seem to be a worthwhile exercise?

Immediately before your last rule (ie. before the # Send Requests To Front Controller... comment) you can add something like the following:

You need parenthesis around what you want to capture. Back-references indices start with '1':

You can have it like this: