<div>
See my comments:
<pre><code class="code-10 nolinks" id="code-20-40429925-1"># Declare a virtual host answering to any domain name on port 80&lt;VirtualHost *:80&gt;
#stand-alone instances
# include the file conf/my_application.conf. Any directives found in that file will apply to this 
# scope as if they were written here individually
include conf/my_application.conf
# Turn on the rewrite engine
RewriteEngine On
# The next three directives make up a single rewrite
# the RewriteRule is matched first. If it is matched, the two RewriteCond directives are
# tested. If the conditions pass, the request is finally rewritten
#
# the request is on port 80 
RewriteCond %{SERVER_PORT} 80
# the requested host is not an empty string
RewriteCond %{HTTP_HOST} !^$
# for every request, capture the entire content of the request string
# and forward to the requested host with the same request string
# the forward is done as a 301 redirect, with no URL escaping of the
# string, and this will be the last rewrite processed
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L,NE]
# end the virtual host definition
&lt;/VirtualHost&gt;
</code></pre>
 
Note that this rewrite does nothing useful, and will likely result in an endless redirection loop. 
 
You can read more about rewrites in the <a href="http://httpd.apache.org/docs/current/mod/mod_rewrite.html" rel="ugc">Apache docs</a>.
</div>

<div>
Thanks for the help Steve, 
 
On Line number 9 you mention RewriteRule is matched first but we have declared 2 RewriteCond first then 1 RewriteRule. 
 
Also we we are starting rewrite engine with 'RewriteEngine On' and now how are are stopping it? 
 
Could you please give a example URL and help me to understand how it flows in such rule? Thanks :-)
</div>

<div>
RewriteEngine stops where section (Like VirtualHost) ends. 
 
Since your rewrite rule runs on http host checking for port 80 is moot. You can as well replace all rewrite rules with one line 
Redirect / <a href="https://site_name_.com/" rel="ugc">https://site_name_.com/</a>
</div>

<div>
&gt;&gt;&gt; you mention RewriteRule is matched first but we have declared 2 RewriteCond first then 1 RewriteRule. 
 
That is correct. &nbsp;Take a look at <a href="http://httpd.apache.org/docs/current/rewrite/tech.html#InternalRuleset" rel="ugc">mod_rewrite's flow diagram</a>. &nbsp;Note that the rule's pattern is matched, then conditions are processed, then the rewrite is applied. 
 
&gt;&gt;&gt;&nbsp;we are starting rewrite engine with 'RewriteEngine On' and now how are are stopping it? 
 
That question is a little ambiguous. &nbsp;The <a href="http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriteengine" rel="ugc">RewriteEngine directive</a> simply tells mod_rewrite to process any rules within this scope. &nbsp;You can also use &quot;RewriteEngine Off&quot; to force mod_rewrite to ignore any rules. &nbsp;If mod_rewrite is processing rules, i.e., &quot;RewriteEngine On&quot;, the every rule in the request's scope is applied to each request. &nbsp;The application of rules ends when one of the following conditions is met: 

<div class="bullet">
there are no more rules, 
</div>
<div class="bullet">
the request is redirected externally, either on a successful rule application with a [R] modifier, or a redirect to an external URL,
</div>
<div class="bullet">
a rule with the [L] or [END] modifiers are successfullt applied
</div>
 
Also, as gheist mentioned, the ruleset you posted is really just a return to the current request. &nbsp;I was incorrect in my earlier assertion that it would result in a redirect loop...the rule is redirecting to the https version of the same request. &nbsp;This rule enforces https on all requests: 
 
1) Apache receives the request for http://mydomain.com/page.htm 
2) mod_rewrite matches &quot;/page.htm&quot; to the rule's ^(.*)$ pattern 
3) mod_rewrite passes the condition %{SERVER_PORT} = 80 
4) mod_rewrite passes the condition %{HTTP_HOST} != &lt;blank string&gt; 
5) mod_rewrite redirects the request to https://mydomain.com/page.htm&nbsp;with a 301.
</div>

<div>
2) would match any request 
3) would match all requests on that virtual host 
4) will be always true again on the virtualhost context 
5) Actually rewrite effectively in this place is 
Redirect perm / <a href="https://%" rel="ugc nofollow">https://%</a>{HTTP_HOST}/ 
 
Sure it is nice to dig some config snipplets on the internet, but what is the value of them that you do 3 NOOP checks?
</div>

<div>
So when I access <a href="http://client.myapplication.com" rel="ugc">http://client.myapplication.com</a>&nbsp;then I see it redirects to the address bar as <a href="https://client.myapplication.com/myapplication" rel="ugc">https://client.myapplication.com/myapplication</a>&nbsp;then again it redirects as <a href="https://client.myapplication.com/myapplication/web/login" rel="ugc">https://client.myapplication.com/myapplication/web/login</a> 
 
All of this is happening due to below config? 
 

<pre><code class="code-10 nolinks" id="code-20-40430931-1"># Declare a virtual host answering to any domain name on port 80&lt;VirtualHost *:80&gt;
#stand-alone instances
# include the file conf/my_application.conf. Any directives found in that file will apply to this 
# scope as if they were written here individually
include conf/my_application.conf
# Turn on the rewrite engine
RewriteEngine On
# The next three directives make up a single rewrite
# the RewriteRule is matched first. If it is matched, the two RewriteCond directives are
# tested. If the conditions pass, the request is finally rewritten
#
# the request is on port 80 
RewriteCond %{SERVER_PORT} 80
# the requested host is not an empty string
RewriteCond %{HTTP_HOST} !^$
# for every request, capture the entire content of the request string
# and forward to the requested host with the same request string
# the forward is done as a 301 redirect, with no URL escaping of the
# string, and this will be the last rewrite processed
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L,NE]
# end the virtual host definition
&lt;/VirtualHost&gt;
</code></pre>
</div>

<div>
Steve, How apache checks if 'URI changed' as mentioned in your below diagram: <a href="http://httpd.apache.org/docs/current/rewrite/tech.html#InternalRuleset" rel="ugc">http://httpd.apache.org/docs/current/rewrite/tech.html#InternalRuleset</a> 
 
Thanks for helping
</div>

<div>
Can you post output of httpd -V ? 
You refer to the documentation of development version of apache. That document is not relevant for any usable version of apache of today.
</div>

<div>
@gheist 
&gt;&gt;&gt;&nbsp;You refer to the documentation of development version of apache. 
 
That document is for Apache 2.4, which is the most up-to-date production version of Apache. &nbsp;The <a href="http://httpd.apache.org/docs/2.2/rewrite/tech.html#InternalRuleset" rel="ugc">Apache 2.2 version of the same document</a> shows the same overall flow, but with a little less detail. 
 
All of my links are pointing to v2.4 documentation. &nbsp;To see the v2.2 equivalent page, change the word &quot;current&quot; to &quot;2.2&quot; in the respective link. 
 
 
@beer9 
&gt;&gt;&gt;&nbsp;How apache checks if 'URI changed' as mentioned in your below diagram 
 
You would have to check the source code for Apache or mod_rewrite to be sure, but I imagine it is a simple string comparison. &nbsp;The URI is generally changed if a rewrite is successfully applied. &nbsp;The final branch of that decision making simply determines if: 
 
a) no rewrites were done, in which case, serve the originally requested resource, 
b) a rewrite was successful, and the new URI points to a resource on the same server. &nbsp;In this case, re-submit the new URI into Apache's request chain, 
c) a rewrite was successful, and the new URI points to an external location. &nbsp;In this case, Apache returns a 3xx response to the client telling them to go elsewhere.
</div>

<div>
Thanks for the help :-) 
 
Does rewrite and redirect add any HTTP header to request/reponse? (like X-Forwarded-For) ??
</div>

<div>
No it adds just 301/302 with target address, resulting request to new place &nbsp;has referer of redirect page.
</div>

<div>
<div class="content wysiwyg-content">
I have following in my httpd.conf file in a web server 
 

<pre><code class="code-1 nolinks" id="code-10-28552852-1">&lt;VirtualHost *:80&gt;
#stand-alone instances
include conf/my_application.conf
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{HTTP_HOST} !^$
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L,NE]
&lt;/VirtualHost&gt;
</code></pre>
 
I would like to understand what it does?
</div>
</div>

I have following in my httpd.conf file in a web server

(CODE)

I would like to understand what it does?

How RewriteEngine works in Apache web server?

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.