httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lester Caine <les...@lsces.co.uk>
Subject Re: [users@httpd] Upgrading owncloud to 2.4
Date Mon, 05 Aug 2013 15:23:48 GMT
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 <lester@lsces.co.uk> 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 <lester@lsces.co.uk> 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.
>>>>
>>>>> <IfModule mod_rewrite.c>
>>>>> 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]
>>>>> </IfModule>
>>>>
>>>>
>>>>
>>>> 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


Mime
View raw message