<div dir="ltr"><div class="gmail_quote">On Fri, Apr 22, 2011 at 12:57 PM, Hetz Ben Hamo <span dir="ltr"><<a href="mailto:hetzbh@gmail.com">hetzbh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 .8ex;border-left:1px #ccc solid;border-right:1px #ccc solid;padding-left:1ex;padding-right:1ex">
<div dir="rtl"><div dir="ltr"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 .8ex;border-left:1px #ccc solid;border-right:1px #ccc solid;padding-left:1ex;padding-right:1ex"><div class="gmail_quote">
<div>Let's continue then... since this domain (VirtualHost) won't be serving any OTHER traffic, there's no point at conditioning the rewrites (and putting them into our debug process). RewriteCond can be removed. <br>
</div></div><br></blockquote><blockquote class="gmail_quote" style="margin:0 .8ex;border-left:1px #ccc solid;border-right:1px #ccc solid;padding-left:1ex;padding-right:1ex">You've also placed a RewriteOptions Inherit. Which means the rewrite engine inherits some configuration from the global configuration - which is unknown to us. Unless you have a very good reason - please remove that too.<br>
<br></blockquote></div><div>Both conditions were left from another configuration which was global indeed.</div></div></div></div></blockquote><div><br>Hmm no, point was that "RewriteOptions Inherit" _adds_ complexity to our issue, where it adds (maybe) other options we might not be interested at. So unless there's a very good reason (and I don't think there is, in this scenario...) - it should be removed.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); border-right: 1px solid rgb(204, 204, 204); padding-left: 1ex; padding-right: 1ex;"><div dir="rtl"><div dir="ltr">
<div class="gmail_quote"><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 .8ex;border-left:1px #ccc solid;border-right:1px #ccc solid;padding-left:1ex;padding-right:1ex">
Finally, if all else fails; Why do you need RewriteRule anyways? :)<br><br>What's wrong with:<br><br>Redirect permanent / <a href="http://vps.net.bz/" target="_blank">http://vps.net.bz/</a><br><br></blockquote></div>
<div>First, it doesn't move the parameters. if someone comes to <a href="http://blog.hetz.biz/?p=300" target="_blank">blog.hetz.biz/?p=300</a> - it should go to <a href="http://vps.net.bz/?p=300" target="_blank">vps.net.bz/?p=300</a></div>
<div><br></div></div></div></div></blockquote><div><br>That's not what I understand from the documentation: <a href="http://httpd.apache.org/docs/current/mod/mod_alias.html#redirect">http://httpd.apache.org/docs/current/mod/mod_alias.html#redirect</a> - but again I may be missing something.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); border-right: 1px solid rgb(204, 204, 204); padding-left: 1ex; padding-right: 1ex;"><div dir="rtl"><div dir="ltr">
<div class="gmail_quote"><div></div><div>Second, this requires a new virtualhost (for <a href="http://vps.net.bz" target="_blank">vps.net.bz</a>) - am I right?</div></div></div></div></blockquote><div><br>Which you already have at the moment, no? As there's no ServerAlias in that VirtualHost you pasted, I understood <a href="http://vps.net.bz">vps.net.bz</a> is on a different vhost.<br>
<br>Not that I understand what's wrong with a one-line VHost for the old hostname. From some reason I take this type of configuration cleaner and easier to debug later (and could also very be more efficient performance-wise. or not. :))<br>
<br>Anyways that was suggestion if all else has failed. My experience is that it's easier to solve the issue by braking it up to as many probable parts as possible. Leaving just the RewriteRule/Redirect will tell us if the problem was with the RewriteCond / Inherit. If it works, you can add more layers later...<br>
<br>-- Shimi<br></div></div></div>