Try to restore your files from a backup. Most probably other things got
corrupted not just the .htaccess
On Thu, Feb 26, 2015 at 4:08 PM, Bremser, Kurt (AMOS Austria GmbH) <
kurt.brem...@allianz.at> wrote:
> Maybe the filesystem was damaged? Try fsck and remove the .htaccess
> file, if you don'
On Thu, Feb 26, 2015 at 6:17 PM, deoren
wrote:
> I thought that having the less restrictive and more path specific block
> beneath the other would allow it to override the less specific block, but so
> far no luck.
Most things are merged/inherited when not overridden, either at a
per-module or p
Hi,
Thanks in advance for reading this and any for help you can provide.
I call myself trying the steps described in various forum, blog and official
documentation recommendations, but I'm still getting unexpected (to me) behavior from
two similar blocks. I even took the example from the serv
A typical 'make install' will just over-write what needs
to be updated, which will likely include all Apache provided
modules.
> On Feb 26, 2015, at 4:49 PM, Daryl Rose wrote:
>
> Just to preface this question, I am not very knowledgeable in Apache. I did
> not setup this environment and have
Just to preface this question, I am not very knowledgeable in Apache. I did
not setup this environment and have absolutely know idea how its configured.
This issue was assigned to me, and I have to resolve it, so I am turning to the
user community for help.
Can I upgrade from 2.4.10 to 2.4.12?
On Thu, Feb 26, 2015 at 11:25 AM, zBit wrote:
> RewriteCond %{HTTPS} =on
>
> Is there any workaround for this? So far, I tried to disable mod_ssl
> completely and also checked modules hooks and it seems that
> environment files are loaded before the rewrite module.
%{HTTPS} does not look up an e
Hello everyone!
I have Apache SSL virtuals behind the Nginx proxy defined with this directive:
SetEnvIf X-Forwarded-Proto https HTTPS=on
Users often use the following rewrite rule in their htaccess files for
detecting SSL connection, but the variable HTTPS is not treated as
expected:
RewriteCon
Thanks for the responses, including the info about what response codes are
cachable. My expectations would have been that 404's wouldn't have been cached,
but was questioning / doubting this assumption / expectation as I'm struggling
to explain the behaviour being reported:User reports their web
On Thu, Feb 26, 2015 at 1:00 PM, Yann Ylavic wrote:
> On Thu, Feb 26, 2015 at 10:21 AM, Paul Beckett
> wrote:
>> Is there any way to restrict what HTTP response codes are cached by Apache,
>> ideally I would like to only cache 200,301,302 responses.
>
> It is not possible to specify some particu
On Thu, Feb 26, 2015 at 10:21 AM, Paul Beckett wrote:
> Is there any way to restrict what HTTP response codes are cached by Apache,
> ideally I would like to only cache 200,301,302 responses.
It is not possible to specify some particular status mod_cache would
or not cache, it is solely controlle
I'm running Apache 2.4.10, and using mod_cache_disk . Some of my web content is
from flatfiles stored on an NFS export. I think these are occasionally going
AWOL, resulting in 404 responses, which appear to then be cached by Apache.
Is there any way to restrict what HTTP response codes are cached
Also found this:
http://stackoverflow.com/questions/15607300/htaccess-pcfg-openfile-unable-to-check-htaccess-file-ensure-it-is-readable-and
In short, check the whole directory tree from root up. And do it after a su -
to the userid that is specified in the httpd.conf (nobody or similar)
One of th
Maybe the filesystem was damaged? Try fsck and remove the .htaccess file, if
you don't need it at all.
Kurt Bremser
Newton was wrong. There is no gravity. The Earth sucks.
Von: Chris Arnold [carn...@electrichendrix.com]
Gesendet: Donnerstag, 26. Februar 2015 08:2
13 matches
Mail list logo
