Monday, November 21, 2005

Found memory leak


I think that I have found the problem that I was having where it appeared that apache was leaking.


I had some mod_rewrite rules that forward request from where this blog was hosted to the new domain name.



<IfModule mod_rewrite.c>

RewriteEngine on

RewriteRule ^/blog$ http://www.paulstimesink.com/ [L,R]

RewriteRule ^/blog/(.*) http://www.paulstimesink.com/$1 [L,R]

</Ifmodule>


I changed this to:



Alias /blog /<path_to_LifeType>


When people browse the old url, the url that they will see in their browser will be the old one, but I think that is reasonable.







The reason that I think that this is the problem is that when using redirects for two hosts on the same machine, this causes double of the connections open at the same time. The first will be the original connection. Then the redirect, will cause the browser to open a second connection. Most browser should close the previous connection before opening the next, but some browsers may not do this.

1 comment:

  1. Strange as I would have thought those Rewrite Rules would have been well tested by now. How long have you been running with that change for?

    ReplyDelete

Seamless Local Control: Integrating WeatherFlow with Home Assistant Across VLANs

I've been pleased with my Home Assistant setup for some time now. One of my main focuses has been achieving local control. This ensures...