> You missed it:
> http://search.cpan.org/author/SAMTREGAR/HTML-Template-2.6/Temp
late.pm#NOTES
Ah. When the section begins "If you're a fanatic about valid HTML" it
becomes more clear why I missed that. :-)
Thanks,
Fran
> Change that to:
>
>
You mean don't you? Or did I miss the
secret stealth hide-your-tags-in-html-comments feature? :-)
-Fran
> In a good OO system with objects
> representing the
> data model, I found it exhausting to use H::T when I could
> just to this
> in TT:
>
> [% user.name %]
>
>
> Am I just being stupid, or are there better ways of doing
> these things
> in H::T?
I'm a little late to the dance but I ge
The only way to expire a basic auth login is to close all instances of the
browser. This is not a mod_perl limitation; it's just the way basic auth
works.
It's pretty easy to spin a mod_perl authentication handler to take the place
of basic auth, though. There's some recipes in the cookbook.
-F
IIRC, we just had a thread on this a week or two back. We discussed a
couple of solutions Randal had turned into columns in addition to some other
suggestions. Maybe peek through the archives? The thread title I believe
was 'Please wait Handler' but talked about ways to serve the data piecemeal
We had this same problem a while back. One of our developers pecked at it
for a couple of weeks off and on, and in our case it turned out to be
Javascript. We had some links to the pages that would spin infinitely that
looked like:
Link
we changed them to this:
Link
and the problems went awa
This is going to be a somewhat preliminary "feeler" post because we are not
yet able to fully describe or recreate the bug we're seeing, but I'm hoping
some of you have seen something similar.
We use Apache::Session::File as the storage module for our Apache::Session
sessions. I have written an
> Do you develop with an xterm tailing the logs, an emacs
> window (or other
> editor) to edit the script and/or the packages (and on some occassions
> httpd.conf), and a web browser (on an alternate virtual
> desktop)?
Bingo. :-)
Do you
> pepper code with :
>
> print "option:" . $option{$f
> I wonder if telecommuting plus occasional travel for
> face-to-face would
> sell better than pure telecommuting. Is this done very often
> in telecommute
> situations?
This is exactly what I hope to propose if the need arises in my situation.
Would love to hear from others who have had succe
> I suspect that there are actually quite a few people on this
> list that would
> _love_ to do mod_perl full time.
>
> open up to telecommuting and I suspect you would soon find
> yourself fully
> staffed.
Definitely. Put me in this category. I'm faced with having to relocate at
some po
> 1) Database Objects in Perl
>
> This talk would focus on the database mapping options for Perl,
> including modules like Tangram, Class::DBI, SPOPS, etc. It would
> examine the differences in features, ease of use, and performance and
> include a set of hand-coded classes using straight DB
Though I have not encountered this problem personally, it's been discussed
here a few times before, and a google search of "PerlRequire running twice"
turned up a page full of promising leads, so I suggest peeking at the
archives and google.
-Fran
> -Original Message-
> From: Andreas Ri
Thanks, finally found the right combination...
{
local $| = 1;
$r->content_type('text/html');
$r->send_http_header;
print "Testing...\n";
}
-Fran
-Original Message-
From: Issac Goldstand [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 4:28 PM
To: [EMAIL P
That doesn't work for us. It seems that the browser also maintains a
buffer, because if I loop the please wait message 1 times, it does show
up immediately. I suspect possibly there's some massaging we can do to the
header?
Thanks,
Fran
-Original Message-
From: Issac Goldstand [mai
I would like to have some of the page display while the rest of the data for
the page is still being retrieved (i.e. a "Please wait, this operation takes
several seconds..." kind of message). I thought (perhaps naively) that a
print "Please wait.\n"; at the beginning of my handler would acco
I'm having a slight problem using AuthCookie in our app because our app
(unfortunately) is a frames-based interface. To summarize the problem and
efforts I've made to date, my goal is to be able to display a message on the
login page telling them why they are seeing the login page. Options are:
After further review, the problem was CGI.pm. CGI.pm doesn't appear to get
'reset' on an internal_redirect (I'm not familiar with CGI's support for
mod_perl, so maybe this should have been obvious!) so it was still holding
the old parameter values. A quick install of Apache::Request and a call
I've got a bit of a better grasp on the problem nowI think it's an
interaction with POST data...
I have a form in foo.html
...other form fields...
I submit this form, and in /rms/admin, it gets handled like this
# suck in form values, stick them in objects, blah blah, then get
I call a page, /my/script1?task=foo which does some things and then needs to
redirect to /my/script2?task=bar. However, putting
$r->internal_redirect('/my/script2?task=bar');
doesn't seem to work as script2 is seeing task=foo rather than task=bar.
Looks like the internal_redirect is also pass
> Can anyone advise me on how to build
>apache server with ssl and openssl and
>using mod perl.
It's right there in the user's guide.
http://perl.apache.org/docs/1.0/guide/install.html#mod_perl_and_mod_ssl___op
enssl_
-Fran
20 matches
Mail list logo
