Скачать или смотреть How to Rewrite and Replace Get Parameters in URLs Using .htaccess

Master the techniques of `URL rewriting` to convert query parameters into user-friendly URLs in `.htaccess` for your website.
---
This video is based on the question https://stackoverflow.com/q/70747773/ asked by the user 'qadenza' ( https://stackoverflow.com/u/3044737/ ) and on the answer https://stackoverflow.com/a/70748225/ provided by the user 'MrWhite' ( https://stackoverflow.com/u/369434/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: rewrite and replace value of a get param inside url

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
A Guide to Rewriting Get Parameters in URLs with .htaccess

In the world of web development, maintaining clean and user-friendly URLs is crucial for both user experience and search engine optimization (SEO). One common challenge developers face is how to rewrite and replace values in GET parameters inside a URL. In this guide, we'll explore how to take a URL like example.com/index.php?c=bs and convert it into a more readable format, such as example.com/blue-sky. This process not only simplifies the URL but also helps in making it more SEO-friendly.

Understanding the Problem

Suppose you have a website where the original URL contains parameters, such as:

example.com/index.php?c=bs

or just example.com/?c=bs

You prefer to have a more visually appealing address in the browser's address bar:

example.com/blue-sky

Your goal is to implement a solution in the .htaccess file, which will seamlessly redirect incoming requests with parameters to your new friendly URL while also maintaining internal access to the original page.

Step-by-Step Solution

Step 1: Enable URL Rewriting

First things first – you need to make sure that your server is set up to perform URL rewriting. This is done using the mod_rewrite module of Apache. Here’s how to start:

[[See Video to Reveal this Text or Code Snippet]]

This line of code enables the rewrite engine for your site, allowing you to set up rules for URL manipulation.

Step 2: Redirect to the Friendly URL

Next, we need to create a rule that will redirect requests from the old URL to the new, friendly URL. For this, use the following code in your .htaccess file:

[[See Video to Reveal this Text or Code Snippet]]

Breakdown of this rule:

RewriteCond: This checks if the QUERY_STRING matches c=bs.

RewriteRule: If the condition is met, it redirects to /blue-sky.

QSD: This flag discards the original query string so that the URL does not show ?c=bs in the address bar.

R=301: This denotes that it is a permanent redirect, which is favorable for SEO.

L: This indicates that this is the last rule to process if the condition is met.

Step 3: Internally Rewrite to Maintain Functionality

Finally, we need to ensure that requests for /blue-sky are correctly internally routed back to the original URL, so the web application can process it properly. Here’s the rewrite rule for that:

[[See Video to Reveal this Text or Code Snippet]]

Key points of this rewrite:

RewriteRule: Checks if a request is made for /blue-sky and routes it to index.php?c=bs.

QSA: This flag allows any additional query parameters to be passed along. For example, if a user accesses /blue-sky?foo=1, it would internally become index.php?c=bs&foo=1.

END: This stops further rewriting and prevents the rewritten URL from triggering the rewrite rules again, which avoids an endless loop.

Why Your Initial Attempt Didn’t Work

You might have tried using different rules that didn’t yield the desired result. Let's look at why they fell short:

Malformed Redirect: You attempted to use %1 to redirect which resulted in an empty backreference causing a malformed redirect.

Potential Loop Issues: The use of L in your second rewrite rule potentially initiated a redirect loop due to the recursive nature of the rules.

By implementing the solutions outlined above, you should be able to achieve the desired behavior, transforming user-unfriendly URLs into clean and SEO-friendly ones seamlessly.



In conclusion, having clean URLs not only enhances user experience but also improves your site’s visibility in search engines. Implementing these .htaccess rules is a crucial step in creating a polished web presence. If you encounter further challenges, don’t hesitate to reach out for more help – happy rewriting!