On 28.02.2012 07:23, Harsimranjit singh Kler wrote:
Hi
Thanks for reply
i have these setting for build::
Server version: Apache/2.2.17 (Unix)
Server built:Apr 19 2011 21:11:59
Server's Module Magic Number: 20051115:25
Server loaded:APR 1.4.2, APR-Util 1.3.10
Compiled using: APR 1.4.2, APR-Ut
Hi
Thanks for reply
i have these setting for build::
Server version: Apache/2.2.17 (Unix)
Server built: Apr 19 2011 21:11:59
Server's Module Magic Number: 20051115:25
Server loaded: APR 1.4.2, APR-Util 1.3.10
Compiled using: APR 1.4.2, APR-Util 1.3.10
Architecture: 64-bit
Server MPM:
On Tue, 2012-02-28 at 11:01 +0530, Harsimranjit singh Kler wrote:
> Hi
>
> i am currently using httpd 2.2.17. i want to upgrade to newer higher
> version.
>
> Please let me know which one stable version and i can use for long
> time.(mainly i have to use modjk and ssl support)
>
> regards
> Har
On Mon, 2012-02-27 at 10:32 +, Lester Caine wrote:
> Spring cleaning time ...
>
> I have a number of older dynamically built sites that are still using
> .htaccess
> to limit access to areas that only PHP needs to read. This is the simply way
> of
> doing things, but I am looking to curre
On Mon, 2012-02-27 at 18:37 +1000, Nick Edwards wrote:
> I note that the allow/deny old method is deprecated, but I find the
> lack of examples problemsome in trying to convert to the newer method,
> which I guess we should be doing to avoid bad habbits.
>
> DIR
> Order allow,deny
>
>>> I have some settings inside a block that I need applied
>>> to all but those same files:
>>>
>>> /folder/file.html
>>> /folder/file.txt
>>>
>>> Can that be done or do I need to use a separate VirtualHost for those
>>> files?
Does anyone know if this can be done?
- Grant
On Mon, Feb 27, 2012 at 1:00 AM, Julie Xu wrote:
> Hi
>
> I want do rewrite on file proxy.pac. that means if a client use IE from
> 10.1.1.0/24 to query proxy.pac, will get proxy1.pac, and other get
> proxy.pac.
>
> I have did:
>
>
> RewriteEngine On
> RewriteCond %{REMOTE_ADDR}
Spring cleaning time ...
I have a number of older dynamically built sites that are still using .htaccess
to limit access to areas that only PHP needs to read. This is the simply way of
doing things, but I am looking to current practice, and the performance hit may
well be something I need to b
I note that the allow/deny old method is deprecated, but I find the
lack of examples problemsome in trying to convert to the newer method,
which I guess we should be doing to avoid bad habbits.
DIR
Order allow,deny
Allow from 1.2.0 127.0.0.1
Satisfy any
...auth DB stuf
