Can you elaborate on this a little bit? I didn't see anything about it in the CPAN listing for this plug-in... (It doesn't surprise me, and yes, my local-box is an Apache2. The host-server, I expect, is gonna be Apache-one-dot-ancient. So the issue's gonna “bite” me regardless...)
Yes, oh Monks, I know that “this is not an Apache support site,” and I certainly respect that. It simply occurred to me that this would probably be a great concentration of “folks who would likely to be able to say ‘oh, yeah...’ and come up with the solution in a hurry. Especially given that we're ultimately talking about a CPAN-plugin (CGI Application Plugin ActionDispatch). I do beg your indulgence and hope that the question is not too-seriously misplaced.
| |
My first reaction was to be pissed...
... Fortunately, I have learned not to respond to my first reaction. I have quite-cheerfully tossed that reaction aside and will say nothing more of it. Rather: “Short and sweet! Thank you!”
Clearly, I am dealing with what is probably also a very-familiar scenario: my local server is running Apache 2-point-latest, but my dark-ages (but che-e-e-e-ep) web-host is running 1-point-who_knows_what. So I have to make sure that the code that I am writing (or... shamelessly importing from CPAN...) will work everywhere. I don't want to do rsync and find myself “madly scrambling” (again...).
It seems to me that several of these venerable CPAN modules have not caught-up with the times. Things like the Apache 2.0 AcceptPathInfo directive, which I am now studying closely based on this post, are not mentioned at all. But they are, obviously, extremely important to me in a situation like this one. I would love to read more in-depth follow-ups to this topic, and I daresay that I cannot be alone in this. We developers (naturally) go for “the latest,” while the web-hosts that run our stuff go for “old.” So, this is great, and I still want to find|know more.
| |