DirectoryAccelNoPass in mod_accel

2001-12-31 Thread Philip Mak

Is there a way to specify an AccelNoPass directive (from mod_accel) that
only affects a certain directory?

For example, consider the following scenario:

AccelPass /~user1/ http://127.0.0.1:8001/
AccelNoPass ~*\.gif$ ~*\.jpg$

AccelPass /~user2/ http://127.0.0.1:8002/
AccelNoPass ~*\.gif$

Someone might want to specify separate AccelNoPass settings for those two
directories. It doesn't seem to work when I put it in Directory though;
I get AccelNoPass not allowed here error.

(I don't actually need this functionality at this point and I think it's
an obscure case, but I felt it was worth pointing out.)




Re: DirectoryAccelNoPass in mod_accel

2001-12-31 Thread Igor Sysoev

On Mon, 31 Dec 2001, Philip Mak wrote:

 Is there a way to specify an AccelNoPass directive (from mod_accel) that
 only affects a certain directory?
 
 For example, consider the following scenario:
 
 AccelPass /~user1/ http://127.0.0.1:8001/
 AccelNoPass ~*\.gif$ ~*\.jpg$
 
 AccelPass /~user2/ http://127.0.0.1:8002/
 AccelNoPass ~*\.gif$
 
 Someone might want to specify separate AccelNoPass settings for those two
 directories. It doesn't seem to work when I put it in Directory though;
 I get AccelNoPass not allowed here error.
 
 (I don't actually need this functionality at this point and I think it's
 an obscure case, but I felt it was worth pointing out.)

No. Both AccelPass and AccelNoPass run in translation phase and 
sets or does not set 'accel-handler'. So if AccelNoPass could run in
Location or Directory then it means that mod_accel needs
to skip 'accel-handler' and found another one instead - mod_accel needs 
to run subrequest.

I think it complicates processing and is not needed in many cases.
Besides in your example case you can use such regexps:

AccelNoPass  ~*\.gif$  ~*^/~user1/.*\.jpg$

Igor Sysoev