<div>
RewriteCond %{SERVER_NAME} ^!www\.<br />
RewriteRule .* %{REQUEST_SCHEME}://<a href="http://www.testpage.com/" rel="ugc">www.testpage.com/</a>
</div>


RewriteCond %{SERVER_NAME} ^!www\.
RewriteRule .* %{REQUEST_SCHEME}://www.testpage.com/ [http://www.testpage.com/]

<div>
OK, but this works only for the root.<br />
<br />
testpage.com -&gt; <a href="http://www.testpage.com" rel="ugc">www.testpage.com</a><br />
<br />
But the rule must work for subdirs and all other requests:<br />
<br />
<a href="https://testpage.com/test/test.html" rel="ugc">https://testpage.com/test/test.html</a>&nbsp;-&gt; <a href="https://www.testpage.com/test/test.html" rel="ugc">https://www.testpage.com/test/test.html</a><br />
<br />
But there must be an exemption like this:<br />
RewriteCond %{<a href="HTTP:Host" rel="ugc">HTTP:Host</a>} ^(testpage\.com)$ [NC]<br />
<br />
Because without this condition, requests with localhost or the ip-adresse also gets rewritten to <a href="http://www.localhost" rel="ugc">www.localhost</a>&nbsp;or <a href="http://www.ip" rel="ugc">www.ip</a>&nbsp;.<br />
<br />
Best regards,<br />
Marcel
</div>


OK, but this works only for the root.

testpage.com -> www.testpage.com [http://www.testpage.com]

But the rule must work for subdirs and all other requests:

https://testpage.com/test/test.html [https://testpage.com/test/test.html] -> https://www.testpage.com/test/test.html [https://www.testpage.com/test/test.html]

But there must be an exemption like this:
RewriteCond %{HTTP:Host [HTTP:Host]} ^(testpage\.com)$ [NC]

Because without this condition, requests with localhost or the ip-adresse also gets rewritten to www.localhost [http://www.localhost] or www.ip [http://www.ip] .

Best regards,
Marcel

<div>
<div class="content wysiwyg-content">
Hi experts,<br />
we have created a rewrite-rule with mod_rewrite on an apache based webserver. The rule should rewrite every request without &quot;www&quot; to a request with &quot;www&quot;.<br />
<br />
testpage.com -&gt; <a href="http://www.testpage.com" rel="ugc">www.testpage.com</a><br />
<br />
Our rule works fine, but when a request uses HTTPS without the &quot;www&quot;, the request is changed to with &quot;www&quot; but on HTTP. Is there a way to hold the protocol?<br />
<br />
Our rules looks like this:<br />
RewriteEngine on<br />
<br />
RewriteCond %{HTTPS} (on)?<br />
RewriteCond %{<a href="HTTP:Host" rel="ugc">HTTP:Host</a>} ^(?!www\.)(.+)$ [NC]<br />
RewriteCond %{REQUEST_URI} (.+)<br />
RewriteCond %{<a href="HTTP:Host" rel="ugc">HTTP:Host</a>} ^(testpage\.com)$ [NC]<br />
RewriteRule .? http(?%1s)://www.%2%3 [R=301,L]<br />
<br />
Best regards,<br />
Marcel
</div>
</div>


Hi experts,
we have created a rewrite-rule with mod_rewrite on an apache based webserver. The rule should rewrite every request without "www" to a request with "www".

testpage.com -> www.testpage.com

Our rule works fine, but when a request uses HTTPS without the "www", the request is changed to with "www" but on HTTP. Is there a way to hold the protocol?

Our rules looks like this:
RewriteEngine on

RewriteCond %{HTTPS} (on)?
RewriteCond %{HTTP:Host} ^(?!www\.)(.+)$ [NC]
RewriteCond %{REQUEST_URI} (.+)
RewriteCond %{HTTP:Host} ^(testpage\.com)$ [NC]
RewriteRule .? http(?%1s)://www.%2%3 [R=301,L]

Best regards,
Marcel

Problems mod_rewrite

A web server refers to the software that helps to deliver web content that can be accessed either through the Internet or through an intranet. The primary function of a web server is to store, process and deliver web pages to clients. The communication between client and server takes place using the Hypertext Transfer Protocol (HTTP). The most common use of web servers is to host websites, but there are other uses such as gaming, data storage, running enterprise applications, handling email, FTP, etc.

Web Servers

The Apache HTTP Server is a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards. Typically Apache is run on a Unix-like operating system, but it is available for a wide variety of operating systems, including Linux, Novell NetWare, Mac OS-X and Windows. Released under the Apache License, Apache is open-source software.

Apache Web Server

Web development can range from developing the simplest static single page of plain text to the most complex web-based internet applications, electronic businesses, and social network services using a wide variety of languages and standards, including the familiar HTML, JavaScript and jQuery, ASP and ASP.NET, PHP, ColdFusion, CSS, PHP, Flex and Flash, but also the implementation of a broad list of standards including XML, WSDL, SSDL, VoiceXML and many more.