Common 301 Redirect Htaccess Rules

Here are some common 301 redirect rules that can be added to an .htaccess file: Redirect a single page: Redirect 301 /old-page.html http://www.example.com/new-page.html

This rule redirects the old page "/old-page.html" to the new page "http://www.example.com/new-page.html". Redirect an entire domain: Redirect 301 / http://www.newdomain.com/ This rule redirects all pages on the old domain to the home page of the new domain. Redirect a directory: RedirectMatch 301 ^/old-directory/(.*)$ http://www.example.com/new-directory/$1

This rule redirects all pages in the old directory "/old-directory/" to the corresponding pages in the new directory "/new-directory/". The "$1" is a backreference to the part of the URL that matches the "(.*)" pattern. Redirect all non-www requests to www: RewriteEngine On RewriteCond %{HTTP_HOST} !^www\.example\.com$ RewriteRule ^(.*)$ http://www.example.com/$1 [R=301,L]

This rule redirects all requests that do not begin with "www" to the corresponding URL with "www". For example, "example.com" would be redirected to "www.example.com". Redirect all requests to HTTPS: RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

This rule redirects all requests to the corresponding URL with "https" instead of "http".


Redirect from an old domain to a new domain that includes the full path and query string


Options +FollowSymLinks

RewriteEngine On

RewriteRule ^(.*) http://www.newdomain.com%{REQUEST_URI} [R=302,NC]



RewriteEngine On: This directive enables the Apache mod_rewrite module, which is required for URL rewriting.

RewriteRule: This is the main directive for URL rewriting. It specifies the pattern to match in the requested URL and the replacement URL to use if the pattern is matched.

^(.): This is the pattern to match in the requested URL. The caret (^) indicates the start of the URL and the dot-star (.) matches any character zero or more times. This effectively matches the entire URL path and query string.

http://www.newdomain.com%{REQUEST_URI}: This is the replacement URL to use if the pattern is matched. It consists of the new domain name, followed by the requested URI (path and query string), which is obtained using the %{REQUEST_URI} variable.

[R=302,NC]: This specifies the rewrite rule flags, which modify the behavior of the rule. The R=302 flag indicates a temporary redirect (HTTP status code 302), which tells clients and search engines that the redirect is temporary and the original URL may be used again in the future. The NC flag makes the pattern match case-insensitive.

Overall, this rule will redirect all requests to the new domain without changing the path and query string, using a temporary redirect.





Comments

Post a Comment

Popular posts from this blog

Shell script to find out aliases and their expiration in cacerts

  #!/bin/bash # Set the path to the Java installation directory JAVA_HOME="/opt/java" # Set the password for the keystore KEYSTORE_PASS="keystore_password" # List all aliases in the keystore ALIASES=$(keytool -list -v -keystore $JAVA_HOME/jre/lib/security/cacerts -storepass $KEYSTORE_PASS | grep "Alias name:" | awk '{print $3}') # Loop through the aliases and get the expiration date for each certificate for ALIAS in $ALIASES; do     # Get the expiration date in human-readable format     EXP_DATE=$(keytool -list -v -alias $ALIAS -keystore $JAVA_HOME/jre/lib/security/cacerts -storepass $KEYSTORE_PASS | grep "Valid from" | awk '{print $3 " " $4 " " $7 " " $6}')     # Print the alias name and expiration date     echo "Alias Name: $ALIAS"     echo "Expiration Date: $EXP_DATE"     echo "" done Replace "/path/to/java" with the path to your Java installation directory, ...
Read more

shell script to scp multiple file to multiple destinations

  #!/bin/bash # Prompt the user for the name of the file to transfer using printf and read commands printf "Enter the name of the file to transfer: " read filename # Prompt the user for the IP addresses to transfer the files to using printf and read commands printf "Enter the IP addresses to transfer the file(s) to (separated by spaces): " read -a ips # Define the username to use for the SCP transfer username="user" # Loop through the array of IP addresses and transfer the file to each one for ip in "${ips[@]}" do     # Use printf to display a message before transferring each file     printf "Transferring %s to %s...\n" "$filename" "$ip"         # Use scp to transfer the file to the current IP address     scp "$filename" "${username}@${ip}:~/" done # Use printf to display a summary message when the transfers are complete printf "Transferred %s to %d IP addresses.\n" "$filename"...
Read more

How to resolve port conflict in websphere

 To resolve port conflicts in WebSphere Application Server on Linux, you can follow the below steps: Determine the port that is in conflict: a. Login in server b. Run the command: ./netstat -an | grep <port> where <port> is the port number that is in conflict. Identify the process that is using the port: a. Run the command: ps -ef | grep <PID> where <PID> is the Process ID (PID) of the process that is using the port. Stop the process that is using the port: a. Use the kill command to stop the process: kill -9 <PID> where <PID> is the Process ID of the process that is using the port. b. Change port in serverindex.xml file if required  c.Stop node and sync with dmgr then start node Restart the WebSphere Application Server: a. Go to the WebSphere installation directory: cd /opt/IBM/WebSphere/AppServer/bin b. Run the command: ./stopServer.sh <server_name> where <server_name> is the name of the server that you modified the port number...
Read more