Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8DC2B10582 for ; Mon, 5 Aug 2013 15:57:13 +0000 (UTC) Received: (qmail 83548 invoked by uid 500); 5 Aug 2013 15:57:10 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 83506 invoked by uid 500); 5 Aug 2013 15:57:10 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 83491 invoked by uid 99); 5 Aug 2013 15:57:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Aug 2013 15:57:10 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Aug 2013 15:57:06 +0000 Received: by mail-ob0-f180.google.com with SMTP id up14so5770909obb.25 for ; Mon, 05 Aug 2013 08:56:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=a168Md4iwfCIrEW4fWwaNosl/YGvqrB2l/Bqex+KhX4=; b=Ce781cXyk8r1Y75SKaWzwjT5wkzQgdcxieUix1ZRhHroIHii6HOrHpgsEdLmRlrNxy 9clcQd4GrX2b+eAbiALWCMjkcPLKeDN3e2uTFY6VGcFF72YxI5xcetHa1kh2iiTtrXr6 117dBVyrXAFz/Tm7qES238AoMLnDv0up9Olcg6uFtsv1wAaDRSuMXN93yDMBf12XKfiF lC70eK4a0Js9IG6S23fCwLMOBwAro42tefXvCN/i8EQTNw9myXOjbsXz2nQBLUzp5oVZ x99LyKTvi/z6KgQA6vtYJ5V/NbmB9HvbdLzauc2EKydUB9radPAjMilZkY7CIImZhDdY QnoA== MIME-Version: 1.0 X-Received: by 10.43.137.65 with SMTP id in1mr1700939icc.103.1375718184956; Mon, 05 Aug 2013 08:56:24 -0700 (PDT) Received: by 10.42.215.4 with HTTP; Mon, 5 Aug 2013 08:56:24 -0700 (PDT) In-Reply-To: <51FFC384.3010601@lsces.co.uk> References: <51FD7F03.4010204@lsces.co.uk> <51FEB11E.4010500@lsces.co.uk> <51FFC384.3010601@lsces.co.uk> Date: Mon, 5 Aug 2013 08:56:24 -0700 Message-ID: From: Jose R R To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQk9yJHWIiLViHWX4a2Q7OoVm77BdyGPBOh+CesI+5lC1ulPu/WoUApAdbCO2MjjzxXAKFnI X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Upgrading owncloud to 2.4 You migrate away from STABLE Apache 2.2.x when you have successfully *tested* your app resources on 2.4.x ELSE you don't disturb those UNTIL you *learn* the new paradigm. Good luck! On Mon, Aug 5, 2013 at 8:23 AM, Lester Caine wrote: > Jose R R wrote: >> >> Apache 2.2.x continues to be the default in stable environments. It is >> irresponsible of GoDaddy, or any (shared?) hosting provider, to >> introduce Apache 2.4 without previous notice as there are significant >> variations from 2.2.x. >> >> GoDaddy support *should* help you with relevant modifications to ease >> your pain: you are their customer. You may also post in the ownCloud >> forums for help indicating that your previous web server was swapped >> from under you. >> >> If all else fails, consider acquiring your own virtual private server >> (VPS) with a traditional or cloud hosting provider. They are usually a >> bit more expensive than shared hosting (low range from $10- $30 >> dollars per instance per month) but you control the underlying >> platform. If you implement this latter option, you can just migrate >> your site to an stable Apache 2.2.x -based environment and it will >> just work as before. > > > I am personally converting all of my hosting to 2.4 and an could not care > less about bad service from Go Daddy and I'm not interested in keeping > services on 2.2! The POINT here is that sites that work perfectly stably on > 2.2 no longer work on 2.4. The reason is that some team made a decision to > break them ... It SHOULD be that the same team now HELPS to make > applications work on THEIR new preferred style of working? I've tried > several of the 'fixes' that I've used for my other sites and those posted on > the owncloud lists as well as fixes posted across a number of other projects > that are now also broken due to 'go daddys' stupid decision. These fixes are > not working, and I can't work out why! All of the other sites I've moved > over are now quite happy with their revised rewrite rules, but there is > something I am missing with this one :( Hopefully the people who developed > these changes in the rules can spot what has gone wrong? Those of us who are > trying to implement the changes need that expert input hence asking here! > > >> On Sun, Aug 4, 2013 at 12:53 PM, Lester Caine wrote: >>> >>> Jose R R wrote: >>>> >>>> >>>> You may find additional helpl here: http://forum.owncloud.org/ >>>> as suggested by: >>>> https://twitter.com/ownClouders/status/364051486671507456 >>> >>> >>> >>> THOSE are the various patches that simply don't work! >>> There have been various fixes for 'go daddy' which has apparently simply >>> switched from 2.2 to 2.4 without actually telling anyone! I've dropped >>> 2.2 >>> onto a new machine simply to get a working address book again, but what >>> is >>> needed is some help from people who actually understand what is needed to >>> migrate the 2.2 re-writes to the newer 2.4 format ... PLEASE! >>> >>> >>>> On Sat, Aug 3, 2013 at 3:06 PM, Lester Caine wrote: >>>>> >>>>> >>>>> >>>>> I'm struggling with conflicting patches to get owncloud working with >>>>> apache2.4 >>>>> >>>>> The existing rewrite setup I know needs reworking but I'm not competent >>>>> enough to sort it out. >>>>> >>>>>> >>>>>> RewriteEngine on >>>>>> RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}] >>>>>> RewriteRule ^.well-known/host-meta /public.php?service=host-meta >>>>>> [QSA,L] >>>>>> RewriteRule ^.well-known/host-meta.json >>>>>> /public.php?service=host-meta-json [QSA,L] >>>>>> RewriteRule ^.well-known/carddav /remote.php/carddav/ [R] >>>>>> RewriteRule ^.well-known/caldav /remote.php/caldav/ [R] >>>>>> RewriteRule ^apps/calendar/caldav.php remote.php/caldav/ [QSA,L] >>>>>> RewriteRule ^apps/contacts/carddav.php remote.php/carddav/ [QSA,L] >>>>>> RewriteRule ^apps/([^/]*)/(.*\.(css|php))$ index.php?app=$1&getfile=$2 >>>>>> [QSA,L] >>>>>> RewriteRule ^remote/(.*) remote.php [QSA,L] >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> https://github.com/owncloud/core/blob/master/.htaccess >>>>> is the full file. >>>>> >>>>> I think I'm getting a valid match in the log file, but nothing is >>>>> appearing in the access log ... Any ideas how to rework this please? > > > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > -- Jose R R http://www.metztli-it.com --------------------------------------------------------------------------------------------- IBM Lotus Symphony supported on GNU/Linux, Mac OS, and Windows. --------------------------------------------------------------------------------------------- Daylight Saving Time in USA & Canada ends: Sunday, November 03 2013 --------------------------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org