[BlueOnyx:06095] Re: rewrite rule

[Jeffrey Pellin]

This is causing me a real headache too. However I'm glad others have
noticed the problem as I just  thought I was going bonkers!

On Mon, 13 Dec 2010 09:29:26 +0100, "Steffan" <general at ziggo.nl> wrote:
> This will happen on every update you do in the domainsettings in the gui
> and
> when creating new sites
> It was a update that changed this.
> 
> I also has asked the developers if it is possible to change back or make
a
> gui option for this
> No reply yet.
> I dont like the option, ist screws up website statistics and my client
are
> asking whats happening
> Manualy you can delete the Lines and restart or reload httpd but next
> change
> it will be back
> 
> Michael, can you tell what document we have to change to prevent this
from
> happening at least till the next update ?
> 
> Thanxs
> 
> Steffan
> 
> 
> -----Oorspronkelijk bericht-----
> Van: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
> Namens Darrell D. Mobley
> Verzonden: maandag 13 december 2010 4:47
> Aan: 'BlueOnyx General Mailing List'
> Onderwerp: [BlueOnyx:06092] Re: rewrite rule
> 
>> -----Original Message-----
>> From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
>> On Behalf Of Darrell D. Mobley
>> Sent: Wednesday, October 27, 2010 10:25 AM
>> To: 'BlueOnyx General Mailing List'
>> Subject: [BlueOnyx:05648] Re: rewrite rule
>> 
>> > -----Original Message-----
>> > From: Darrell D. Mobley [mailto:dmobley at uhostme.com]
>> > Sent: Wednesday, October 27, 2010 10:18 AM
>> > To: 'BlueOnyx General Mailing List'
>> > Subject: RE: [BlueOnyx:05624] Re: rewrite rule
>> >
>> > > -----Original Message-----
>> > > From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-
>> bounces at blueonyx.it]
>> > > On Behalf Of Tjerk Hacquebord
>> > > Sent: Friday, October 22, 2010 9:45 AM
>> > > To: 'BlueOnyx General Mailing List'
>> > > Subject: [BlueOnyx:05624] Re: rewrite rule
>> > >
>> > > So this is the new standard??
>> > > Please make us able to change it back to the redirect like it used
to
>> > > be or selectable per site.
>> >
>> > I have yet to see an official answer as to whether or not this was
>> > going
>> > to be the new default behavior for BlueOnyx software.  Like you, I
>> > would
>> > like to know, so that I can make arrangements on my own servers to
>> > manually edit the httpd configurations for each new site to behave as
>> > before.
>> >
>> > Can anyone, Michael, others, answer this question?
>> 
>> Hmmm, I just looked at one of the more recently created sites on my
>> server
>> and it seems to be redirecting as before. Maybe it has already been
>> changed back?
> 
> Hold on a second...
> 
> Well, I just edited an account's domain name and the GUI added that
dreaded
> non-www-redirect rule when it wasn't there originally.  When I first set
> the
> domain up on a development domain to build the site out, the code looked
> like this:
> 
> <VirtualHost xxx.xx.xxx.xxx:80>
> ServerName siteXX.uhostme.com
> ServerAdmin admin
> DocumentRoot /home/.sites/132/siteX/web
> ErrorDocument 401 /error/401-authorization.html
> ErrorDocument 403 /error/403-forbidden.html
> ErrorDocument 404 /error/404-file-not-found.html
> ErrorDocument 500 /error/500-internal-server-error.html
> RewriteEngine on
> RewriteCond %{HTTP_HOST}                !^xxx.xx.xxx.xxx(:80)?$
> RewriteCond %{HTTP_HOST}                !^siteXX.uhostme.com(:80)?$ [NC]
> RewriteRule ^/(.*)                      http://siteXX.uhostme.com/$1
> [L,R=301]
> 
> When the site was ready to go live, I edited the domain name for the site
> and this is what I got:
> 
> <VirtualHost xxx.xx.xxxx.xxx:80>
> ServerName www.domainname.com
> ServerAlias domainname.com
> ServerAdmin admin
> DocumentRoot /home/.sites/132/siteXX/web
> ErrorDocument 401 /error/401-authorization.html
> ErrorDocument 403 /error/403-forbidden.html
> ErrorDocument 404 /error/404-file-not-found.html
> ErrorDocument 500 /error/500-internal-server-error.html
> RewriteEngine on
> RewriteCond %{HTTP_HOST}                !^xxx.xx.xxx.xxx(:80)?$
> RewriteCond %{HTTP_HOST}                !^www.domainname.com(:80)?$ [NC]
> RewriteCond %{HTTP_HOST}                !^domainname.com(:80)?$ [NC]
> RewriteRule ^/(.*)                      http://www.domainname.com/$1
> [L,R=301]
> 
> I tried removing the server alias to see if that would make that bad
> non-redirect rule go away, but it didn't have any affect.  It sure would
be
> good to know *when* this thing is going to show up and when it isn't
going
> to show up so I wouldn't have to manually check the http configuration
> files
> every time a site is created or edited.
> 
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
> 
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx