in reply to mod_perl and cache?

other than my switch from HTML::Mason to just a normal cgi-script
Uh, which is it? mod_perl like your title says, or CGI, like the body of your message says?

Or is it Apache::Registry, in which case we must wonder if your "cgi" "script" is compliant with the restrictions imposed by that interface, which is most definitely not a CGI interface. See the mod_perl_traps and cgi_to_mod_perl manpages.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Replies are listed 'Best First'.
Re: •Re: mod_perl and cache?
by Flame (Deacon) on Feb 28, 2003 at 21:41 UTC

    As I said, I'm adjusting still. So I'll answer that to the best of my ability. It's configured as was stated above. It's executing under mod_perl (sorry, I usually equate the two, still getting used to the differences as I said, starting to see them). Anyway, I'm not sure what would be incompatable, I'd include the whole script if that would help, but in general, I follow my general coding practices, use strict and 'my'.

    Anyway, since you bring up Apache::Registry, I'm not quite certain on the differences between that and the other options, but it seems closest to what I was looking for.

    The script does run, which I assume it would not do if it was really set up wrong, it just seems that browsers INSIST on caching it, which they didn't do previously.

    Is there anything in particular I should look for?

    Thanks for pointing out my conflicting signals merlyn.




    My code doesn't have bugs, it just develops random features.

    Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

[reply]

In Section Seekers of Perl Wisdom