The filesystem module is MODULE_LOCATION.Yeah, and within the class (like Martin pointed out) they are kept in a
As Martin said and according to the flow chart on the Caudium website
(http://caudium.net/server/docs/modules.rxml), MODULE_FIRST should be
called (in random order) before MODULE_LOCATION (they are).
mapping, which means they're effectively in random order - that is unless
you move any of them to a higher priority (within the priority class they're
random as well). I think we should do something about the randomization -
the behavior should be predictable, be it even alphabetic.
For me it _always_ got called for implicit urls (like site.com/ stuff/) butI did not dig further yet (used a MODULE_PRECACHE). That's maybeIt turned out to be the PATH_INFO module that started to block
related to your problem.
gsessions all
of the sudden... Very frustrating.
You ran into the very same problem than me.
Loaded the gsession module, and according to the CIF path resolver,
gsession is called when my own MODULE_FIRST is called, too.
explicit urls (site.com/stuff/index.html) weren't ever passed to gsession.
Shouldn't we just make the whole stuff into a chain of filters instead?
Unload PATH_INFO and everything is fine.
Well, that's not fine at all because i'm planning to use PATH_INFO in
the very near future :)
After having a quick look at pathinfo.pike, it seems that first_try()
returns 1 when a file exists.
My guess is something is wrong here (but today is meeting day).
There are a lot of things that are wrong about 1.4+ alas :(
Archive powered by MhonArc 2.6.10.