> I am using embperl and apache. When I try using the example
> file distributed with embperl, namely upload.htm, I get the
> following error display in the web browser:
>
>
>
>
> Method Not Allowed
>
>
> The requested method POST is not allowed for the URL
> /file_upload.
On 5/25/06, Todd White <[EMAIL PROTECTED]> wrote:
Shoot! Current circumstances might not allow for a recompiling ofEmbperl. Does anyone know of any possible work around?
The problem comes from a change in behaviour of CGI.pm in versions 3.01+
So you could downgrade CGI.pm. Alternatively, the
Shoot! Current circumstances might not allow for a recompiling of
Embperl. Does anyone know of any possible work around?
Thanks Dirk.
--Todd White
On Thu, 25 May 2006, Dirk Jagdmann wrote:
> > M_TWO
> >
> > Apache/1.3.34 (Unix)
> > Embperl/1.3.6
> > mod_perl/1.29
> > mod_ssl/2.8
M_TWO
Apache/1.3.34 (Unix)
Embperl/1.3.6
mod_perl/1.29
mod_ssl/2.8.25
OpenSSL/0.9.7d
HTML::Embperl 1.3.6
CGI 3.04
What happens when run on M_TWO is that nothing is written to the $content
variable.
Embperl 1.3.6 has a bug concerning File upload. You can try to recompile
Embperl w
>
> [Mon Oct 25 17:45:57 2004] [error] [21920]ERR: 44:
> _base.html(1): Setup of CGI.pm failed: CGI open of tmpfile:
> Permission denied
>
Looks like CGI.pm has problem with it's temporary file. Take a look at
perldoc CGI and search for upload. There you can find how CGI.pm find a
location f
>
> I have 1.3.4 installed now, but it still appears that $fdat{UploadFile} is
> not accessible to the "read" function inside my code called by "Execute".
> However, if I set $UploadFile=$fdat{UploadFile}, then I can "read"
$UploadFile.
>
Then my guess that upgrading to 1.3.4 helps was wrong, but
>version 1.3b7, according to the log
Oh, this is really old. You should upgrade to 1.3.4 ...
>But I want to be able to access %fdat values from inside frag1.epl.
Wouldn't this prevent me from doing that?
You can still access the data in %fdat, it's just not resetup (which doesn't
work) when the
At 3/18/02 09:15 PM, Gerald Richter wrote:
> I'm having a problem with a
file upload when the "read" function is in an
> embperl fragment called by the "Execute" method.
>
>
> When I process the main file, I get a zero-length
"tmpfile.txt", because
> there is apparently nothing for the "read
> frag1.epl runs in a different namespace, where %fdat does not exist.
No, %fdat (as all other special Embperl variables) are imported into all
Embperl pages, so it's the same regardless in which package you run
Gerald
-
Gerald Rich
> I'm having a problem with a file upload when the "read" function is in an
> embperl fragment called by the "Execute" method.
>
>
> When I process the main file, I get a zero-length "tmpfile.txt", because
> there is apparently nothing for the "read" function to read.
>
Which Embperl versio
That's not it. I'm able to access all the values of the %fdat hash from
code within the fragment called by "Execute".
In fact, I can make the fragment display the name of the file uploaded from
my desktop, but for some reason embperl can't "read" it.
At 3/18/02 12:58 PM, Ed Grimm wrote:
>frag
frag1.epl runs in a different namespace, where %fdat does not exist.
If you set EMBPERL_PACKAGE, it supposedly runs everything in that
namespace, but I've not yet gotten flawless results with this (I'm doing
a bunch of non-standard stuff; this could be my problem.)
Ed
On Mon, 18 Mar 2002, Michae
"Gerald Richter" <[EMAIL PROTECTED]> writes:
> That should fix the problem, let me know if it works for you
it did - thanks a lot :)
--
# Thoren Johne - 8#X - [EMAIL PROTECTED]
# Southern Division Classic Bikes - www.southern-division.com
*42=sub{X=>35.56.32.10=>=>=>&{sub{H=>&{sub{P=>&{sub{A=>
> >
> > yes, it works with plain Embperl
> >
> >...
> > with the -X switch, it only occurs the first time.
> >
>
> Ok, this should be enough infos to track it down, I let you know as soon
as
> I have found the bug (will be over the weekend)
>
Goto Embperl.pm and add line 904 "!defined ($import) &
Hi,
> I stumbled on this post you made to the mod_perl mailing list in 1998:
>
This problem was fixed many years ago... CGI.pm did always create a new
filehandle and never destroyed it. (so it had leaked a few bytes for each
upload)
>
> My problem is with very large files. I upload, say, a 100
>
> yes, it works with plain Embperl
>
>...
> with the -X switch, it only occurs the first time.
>
Ok, this should be enough infos to track it down, I let you know as soon as
I have found the bug (will be over the weekend)
Gerald
-
Ge
"Gerald Richter" <[EMAIL PROTECTED]> writes:
> > doing a simple file-upload does not always gives a content-type back
> > with EmbperlObject.
> >
>
> Did you try if it works with plain Embperl (without EmbperlObject) ?
yes, it works with plain Embperl
> > this mostly happens after server-start
> doing a simple file-upload does not always gives a content-type back
> with EmbperlObject.
>
Did you try if it works with plain Embperl (without EmbperlObject) ?
>
> this mostly happens after server-startup, and *sometimes* the content-type
> is set after doing a form data repost.
>
Could y
> How do I determine the file handle in your upload example?
> Where would I put this command in the example?
>
[- if (defined $fdat{ImageName}) {
open FILE, "> /tmp/file.$$";
binmode FILE ;
print FILE $buffer
while read($fdat{ImageName}, $buffer, 32768);
> I wasn't aware there was a binmode. How do you turn this on? Is
> this something from Perl or EmbPerl?
>
It's a standart Perl command. Look at
perldoc -f binmode
Gerald
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
> I'm using Randy Kobes' precompiled Apache distribution containing
> the following:
>
> Embperl 1.3b3/Windows NT 4.0/Apache 1.3.12/ModPerl 1.23/Perl
> 5.6.0
>
> When I use the Embperl upload example, files are getting somehow
> corrupted. The file size is not the same as the original and the fi
> I wrote an embperl script that uploads a file to a web
> server. It works fine on Linux and Macs but not on
> Windows. When I upload a file from a browser using
> Windows 95/98, the file is uploaded to the web server
> but it has 0 bytes in it.
> Here is part of the script that checks a file fro
Hi Jim,
At Wed, 7 Mar 2001 20:11:15 +0100, Gerald Richter <[EMAIL PROTECTED]> wrote:
>>
>> In the second pass, I display the data back to the user
>>
>> while (@buffer = <$UserFile>) {print " $buffer";}
>>
>> and put up a button which will submit a hidden field to indicate the user
>> has accep
>
> In the second pass, I display the data back to the user
>
> while (@buffer = <$UserFile>) {print " $buffer";}
>
> and put up a button which will submit a hidden field to indicate the user
> has accepted the data.
>
> print "";
> print "";
You cannot pass a file within a hidden field, actualy
24 matches
Mail list logo
