Richter [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 03, 2000 1:25 PM
> > To: Ilia Lobsanov; [EMAIL PROTECTED]
> > Subject: RE: help resolve complex mod_perl EPL framework
> >
> >
> > >
> > > sorry, forgot one more thing in step 4... pm reads $
t; -Original Message-
> From: Gerald Richter [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 03, 2000 1:25 PM
> To: Ilia Lobsanov; [EMAIL PROTECTED]
> Subject: RE: help resolve complex mod_perl EPL framework
>
>
> >
> > sorry, forgot one more thing in step 4...
dnesday, May 03, 2000 11:55 AM
> > To: Gerald Richter; [EMAIL PROTECTED]
> > Subject: RE: help resolve complex mod_perl EPL framework
> >
> >
> > Dear Gerald,
> >
> > Still no luck... However, now $optDisableFormData is 0, even
> though I have
> > opti
html
> 5. epl outputs [+ $s +]
>
> All works fine with GET.
>
> arghhh... pulling hair... hopes it's a bug in Embperl...
>
> ilia.
>
>
> > -Original Message-
> > From: Gerald Richter [mailto:[EMAIL PROTECTED]]
> > Sent: Wedn
Embperl...
ilia.
> -Original Message-
> From: Gerald Richter [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 26, 2000 3:49 PM
> To: Ilia Lobsanov; [EMAIL PROTECTED]
> Subject: RE: help resolve complex mod_perl EPL framework
>
>
> >
> > Yes it does print 1. Pro
>
> Ok I have another question. Why doesn't <> work?
>
> It's supposed to set the default to 0, but it's still 3.
>
It does set it to zero, but only when you use the mod_perl handler and not
if you call Execute on your own. If you call Execute on your own, you need
to call the ScanEnvironement be
Ok I have another question. Why doesn't <> work?
It's supposed to set the default to 0, but it's still 3.
Please help.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
>
> Yes it does print 1. Problem still stands. :(
>
You could try to set $ENV{CONTENT_LENGTH} = 0 ; before the call to Execute,
but this really shouldn't be nessecary.
Maybe there is another call that tries to read the POSTed data a second
time?
Gerald
> > >
> > > options => HTML::Embperl::optDisableFormData
> >
> > But I am already using options => 256. Isn't it the same thing?
> >
>
> Yes it is, make sure that it really is set by inserting a
>
> [+ $optDisableFormData +]
>
> inside the called page. Should print 1. Does it?
Yes it does pr
> >
> > options => HTML::Embperl::optDisableFormData
>
> But I am already using options => 256. Isn't it the same thing?
>
Yes it is, make sure that it really is set by inserting a
[+ $optDisableFormData +]
inside the called page. Should print 1. Does it?
Gerald
---
> >
> > All this works perfectly via GET.
> > When using POST, the request hangs at the $r->content point.
> >
> > Why?
> >
>
> I guess your script has already read the POSTed data, before Execute is
> called. Now Embperl, which can't know that the data is already read, tries
> to read it again, a
>
> All this works perfectly via GET.
> When using POST, the request hangs at the $r->content point.
>
> Why?
>
I guess your script has already read the POSTed data, before Execute is
called. Now Embperl, which can't know that the data is already read, tries
to read it again, and hangs, because a
I am using embperl in a non-standard way to take care of old perl code which
has html embedded in it via print statements.
Here is a summarized top-to-bottom (1->2->3) overview of the architecture:
1. legacy.phtml
HTML::Embperl::Execute({ inputfile => 'legacy_pm.epl',
param => ['legacy.pm
13 matches
Mail list logo
