eq = $r->pnotes('apreq')) {
return $apreq;
}
my $new_req = $class->new($r, @_);
$r->pnotes('apreq', $new_req);
return $new_req;
}
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
wrong or is this a known bug ??
Bug, previously unknown.
> Any help ?
It looks to me like there may be a problem in apreq_cookie.c
(it may not be computing the "expires" date correctly for Netscape
cookies). Which version of libapr are you using?
--
Joe Schaefer
--
Reporting bugs:
Joe Schaefer <[EMAIL PROTECTED]> writes:
> It looks to me like there may be a problem in apreq_cookie.c
> (it may not be computing the "expires" date correctly for Netscape
> cookies). Which version of libapr are you using?
If you're using the latest libapr, this
xes are ready; what's missing are the corresponding
tests to ensure the bugs don't reappear.
nb- folks can always add more tests to demonstrate
bugs without necessarily having a corresponding fix.
A patch to the test suite which demonstrates a bug
is absolutely the best kind of bug report.
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
_can_ do what you want with mp2/apreq2, no matter what the content
handler is (it doesn't even need to be perl-related). All you'd need
to do is make sure mod_apreq's filter gets inserted before the
content-handler takes over, and then Apache::Request will provide full
access to th
;first) {
$b->read(my $buffer);
$full_image_data .= $buffer;
$b->remove;
}
I'm sure there are better ways to use the brigade API
though. The C API for brigades has a "flatten" function-
does anyone know if mp2 has glue for that yet?
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
ld be in
apache2's module directory, and libapreq2 should be
alongside libaprutil.
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
d,
not APR::Bucket), but would not destroy the buckets within the
brigade (hmm, does APR::Brigade have a DESTROY method?).
The advantage here is you'd be able to accomplish this
in one or two lines of perl, ie.
my $upload_data = $req->upload('file')->bb->
Geoffrey Young <[EMAIL PROTECTED]> writes:
> Joe Schaefer wrote:
> > my $upload_data = $req->upload('file')->bb->flatten;
>
> oooh, nice. I can definitely see that being a useful idiom.
Not sure if it'd be better for flatten to take $upload_
over
APR::Brigade exposing flatten(). It is part of the C API
after all, eh? Why shouldn't perl programmers have access
to it?
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
od and
marking the output as tainted.
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
my $cookie = $self->{cookie_class}->new($self->apache_req->env,...);
my $apr = $self->apache_req; # (no need to call new() here)
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
you either want
$r->env->status(207); # env() yields Apache::RequestRec obj
or
$r->SUPER::status(207); # Apache::RequestRec is the base
# class for Apache::Request (in mp2)
Not sure if this solves your overall problem,
but it should resolve this part of
ble?
No, your change is fine. AFAICT that comment pertains to an esoteric
problem with object cleanup in libapreq/mp1, but the bug doesn't
seem to be carried over into mp2/apreq2 (the apreq2 test suite has
a test for it).
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/b
The size limit is currently 256K, but the size
will be configurable in future versions.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
marked as tainted),
2) be sure "/path/to/local/$filename" is on the same device
(filesystem) as your temporary directory (see the docs for
Apache::Request::new regarding TEMP_DIR).
3) check the return value of $upload->link, if it's false (undef) then
ther
ice situation more gracefully (by making a full copy
of the tempfile should the internal PerlLIO_link fail).
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ESS)
XSRETURN_UNDEF;
if (PerlLIO_link(fname, name) >= 0)
XSRETURN_YES;
else {
apr_status_t s = apr_file_copy(fname, name,
APR_OS_DEFAULT,
apreq_env_pool(env));
if (s == APR_S
se modules parse cookies, they're only looking
at the *request* headers, since that's where the *incoming* cookies
appear.
IOW, you shouldn't try to set/bake cookies as a means of passing
data from one handler to another one *inside the same request*.
Cookies are a means of passing
you need to be very careful about spooling the post data for
the redirected url. This is basically what mod_apreq.c does in
libapreq2, but it's pretty tricky. Perhaps convincing apreq-dev@
to support xml would be your best bet.
--
Joe Schaefer
--
Report problems: http://perl.apache.
ly returning every param name on the form. Is that
> right?
That is correct. In apache1 the uploads formed a linked list
internally, but that's no longer true in apreq2. In apreq2
$req->upload follows the same interface pattern as $req->param.
--
Joe Schaefer
--
R
anything: $req->upload() works just like
$req->param(), but it is restricted to uploads only. For example
my $upload_table_ref = $req->upload; # APR::Table ref of uploads
foreach my $name (keys %$upload_table_ref) {
my @uploads = $req->upload($name); # Array of Apache::Upload
table will only contain uploads, and since it's a
tied hash, you can iterate over it using keys() or each().
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
e obviously doesn't because I'm trying to upload it...
>
> Do I need to ->bb and then write it?
No, link() will do it for you; use current cvs or apply the patch.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
.
This is the reason why the subsequent "Submit" button is missing from the
params: the parser interpreted its block as being the upload file's contents.
The missing CRLF causes the parser to skip over the boundary string
separating the (empty) file block from the "Submit" but
amp; $PERL_DEBUG
=
Doesn't look like the cvs log is going to be of much help;
perhaps checking the list archives in Feb/March 2000 will
turn up something useful.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
pr_time_from_sec was needed for
the conversion.
- C API [Max Kellermann]
Fix segfault caused by invalid %-escape sequence in query string.
==
Thanks!
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl
The Apache Software Foundation and The Apache HTTP Server Project are
pleased to announce the 2.03 developer release of libapreq2.
The libapreq2-2.03_04-dev.tar.gz package has been released under
the new Apache License version 2.0. The package is now available
through the ASF mirrors
http:/
ember's
Apachecon, and I don't expect Apache::Request to change much between
now and then.
Even so, now is a very good time to try it out, because you actually
may want some things changed before we "stabilize" it :-). There
are plenty of open issues in the httpd-apreq-2 ST
uming
> that you had mp2 installed into Apache2/ subdir). You may want to
> report all the details to the apreq-dev mailing list.
+1. The 1.X and 2.X versions of Apache::Request should happily coexist
if mp2 was configured with MP_INST_APACHE2=1. Only the installed Unix
manpages will o
chain, which means it'll call *your* input filter in order to
get at the requested POST data. It looks like you managed to carefully
avoid the infinite recursion in your example, but I'm not sure the
underlying Apache::DECLINED perl magic is smart enough to handle the
reentry- thus the 502.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
> > my $r = $f->r;
>
> wow, a FilterInitHandler in the wild. guess it was a good idea to
> support that after all ;)
IIRC apreq-as-filter was part of the motivation for httpd to even
implement the filter init hook, so yeah, that *was* a good idea :-).
--
Joe Schaefer
--
just link
http://cvs.apache.org/~joes/libapreq2-2.04-dev/docs/html/modules.html
A more permanent link on the apreq website will be available before the
next release.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
Lis
le.
>
> running perl Makefile.PL will not detect this dependency.
It's supposed to, so let's try to fix that.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
personally
involved in maintaining those tables.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
tter
> construct I should be using?
I haven't tested this, but it should be safe to forcibly re-bless
Cparam> into an APR::Table object and do what you want
(without breaking anything). Do not try this with $req->args or
$req->body though.
--
Joe Schaefer
--
Report problems: htt
ed support for tempname
to httpd-apreq-2's current-cvs. I don't know what sort of security
implications you are concerned about, but perhaps the best thing to do
is simply not use tempname, instead using link() - and then delete the
linked file yourself once the external app is done with
Kemin Zhou <[EMAIL PROTECTED]> writes:
> Joe Schaefer wrote:
[...]
> >Despite my past grumblings to the contrary, I've added support for
> >tempname to httpd-apreq-2's current-cvs.
[...]
> Thanks for the help. The tempname is not available in mp2.
You m
tforms. I've seen this on FreeBSD, for
example.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
"Ken Burcham" <[EMAIL PROTECTED]> writes:
> Hey guys,
>
> I submitted a bug report to [EMAIL PROTECTED] and it got returned
> without comment... (maybe it was the wrong place?) so I guess i'll
> post it here since I know Joe Schaefer monitors this lis
ozilla to submit the form) yet. Changing the enctype
just changes the parser. Since the mfd parser seems ok
with your form-data, the problem likely lies in the urlencoded
parser in libapreq2/src/apreq_parsers.c.
Still digging though... any chance you could test this
against current-cvs for ap
Joe Schaefer <[EMAIL PROTECTED]> writes:
[...]
> Still digging though...
Bug found in src/apreq_parsers.c:split_urlword.
The problem is that apreq_decode can fail if
a bucket ends in the middle of an escape sequence,
which causes the parser to abort.
This will be fixed before 2.
agent which doesn't understand it.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
<> operator to consume the buckets in $upload->io().
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ed behind
*it*.
However, if you remove the file bucket from the brigade
*before* you read from it, the morphed file bucket created
during the read winds up in limbo, not in the original brigade.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apach
you could also do:
>
>my $bb = $r->upload('file')->bb();
>my $len = $bb->flatten(my $data);
>print OUT $data;
>
> though it's probably less memory-usage effective.
Hah, aren't *you* the guy that asked for $upload->slurp(my $data)?
Stas Bekman <[EMAIL PROTECTED]> writes:
> Joe Schaefer wrote:
> > Stas Bekman <[EMAIL PROTECTED]> writes:
> > [...]
> >
> >>Moving $b->remove to the end makes the code horribly kludgy. It's
> >>better to change the idiom to step through
;ve called $b->read(), because read()
has all kinds of side effects. The rest of this dialog
seems to have taken us nowhere, so I'll just stop here.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiqu
using a slice there?
@{$hash_ref}{$r->param($param)} = (); # values are now undef, not 0
You need the slice syntax to put $r->param($param) in list context.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ou use Apache::Request
in mp2, that's a bug in Apache::Request.
[...]
> Is there any way to retrieve the raw content (and headers)
You could write a input filter that goes in front of HTTP_IN
(protocol or connection type), which would see the byte stream
in raw form (headers unparsed
d work just fine. If not,
please file a bug report.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Joe Schaefer <[EMAIL PROTECTED]> writes:
> Be sure you've got
>
> use Apache::RequestRecIO;
^^^
Sorry, typo- should be Apache::RequestIO.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/m
able to decode binary data with embedded '\0' values in them.
If you can't bring yourself to that, just write your own converter:
sub Vars {
my $req = shift;
map { $_ => join "\0", $req->param($_) } $req->param;
}
I hope this
side of a "s?
Use $t as a hash-ref:
print "$temp = $t->{$temp}\n";
That only prints the first $temp param (unless your iterating
over the table with each(), which magically pulls the current
$temp param). But you probably don't want $temp multivalued
here unless
ase (more on that soon), so it's really up to the
httpd community to determine whether or not httpd-2.2 users will
benefit from it.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette:
perl auth handler anywhere? If an
auth handler has been coded to use CGI.pm, it will consume
the POST data and your cgi scripts won't ever get it.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List et
atch containing a copyright notice is problematic because
it's no longer clear the author intends for it to be treated as
a typical contribution to the project.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.htm
d of the
API docs? There are plenty of examples in those
already, and the neat thing is that almost all of
them are tested to work as documented.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List eti
for a production environment, but it'd
really help if someone with a good "slow-client" test environment
benchmarked it to see if it helps.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
sponse handler to use two different perl interpreters?
It looks to me like it is possible.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
gs, but I'm
not sure.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
t seems to be the same Cookie
> with CGI, then Apache::Cookie reads it correctly.
IIRC CGI will url-encode the " " as %20, so neither " " nor "+"
will appear in the actual Cookie header. Apache::Cookie is probably
not translating the "+" character into
tice any difference in the
->as_string() outputs for Apache::Cookie versus CGI::Cookie?
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
am using the bake() method? Thanks in
> advance.
libapreq2 is currently using $r->headers_out instead
of $r->err_headers_out, which is why you're not seeing the
cookie on your redirect response. I think the consensus
is that this is a bug in libapreq2-2.04, but I haven't seen
tring'
1=2; path=/; expires=Mon, 15-Nov-2004 16:15:09 GMT
I'm not sure if this is a bug in libapreq2. Any other opinions
out there?
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
jonathan vanasco <[EMAIL PROTECTED]> writes:
> On Nov 15, 2004, at 11:18 AM, Joe Schaefer wrote:
[...]
>> Can you please show us the code which segfaults?
[...]
> sub handler
> {
> my $r = shift;
> my $req= Apache::Request-&g
er. Your server's path should be
/usr/local/apache/bin/httpd
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
runk, thanks to Bojan's recent patch.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
realize it may be too late to stop the impending email
avalance, but *please* move this exciting discussion to the mod_perl
advocacy list [1]. Threads with "marketing" in the subject line
really belong over there, not here.
[1]- [EMAIL PROTECTED]
--
Joe Schaefer
--
Report problem
R, "[libapreq] could not create/open temp file");
+ ap_log_rerror(REQ_ERROR,
+ "[libapreq] could not create/open temp file: %s",
+ strerror(errno));
if ( fd >= 0 ) { remove(name); free(name); }
return NULL;
}
--
Joe Schaefer
1.3_rc2 is httpd-apreq's current cvs; the corresponding tarball is
now available at
http://httpd.apache.org/~joes/libapreq-1.3_rc2.tar.gz
The only change made since 1.3_rc1 is the addition of Stas'
old logging patch, which was mentioned on the modperl list yesterday.
I've tested it on RH linu
The uploaded file
libapreq-1.3.tar.gz
has entered CPAN as
file: $CPAN/authors/id/J/JO/JOESUF/libapreq-1.3.tar.gz
size: 279075 bytes
md5: b40854e91a6210a3af47ef9a875e
It is also available through an apache mirror near you:
http://www.apache.org/dyn/closer.cgi/httpd/libapreq
--
his an appropriate patch?
>
> Have I messed something else up by doing this?
The patch is correct. The problem is that the apreq-dev folks
don't know if it works on OSX or not, so it hasn't been applied.
--
Joe Schaefer
The first developer release of libapreq2 is underway. This
package provides the Perl modules Apache::Request and
Apache::Cookie for modperl-2, and requires the following:
apache2 w/ mod_so: 2.0.46
libapr: 0.9.4
libaprutil: 0.9.4
modperl2: 1.99_09
opriate per-request data; instance() isn't needed there,
so it won't be included in the 2.X releases.
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
for (i = 0; i < arr->nelts; ++i) {
I32 j;
if (!elts[i].key) continue;
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
l(apreq_xs_sv2env(SvRV(ST(0;
for (j = 1; j + 1 < items; j += 2) {
STRLEN alen, vlen;
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
- November 12, 2003 - Perl API [joes]
Fix bogus pool/cookie initializers in Apache::Cookie::set_attr(),
which caused Apache::Cookie::new to segfault. Bug
first reported to modperl list by Wolfgang Kubens.
Thanks!
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info
age to improve now is for folks to start exercising
the code. libapreq2 is a full order of magnitude more complex than
libapreq1, which is why there are so many tests (over 100) already in
the package. But there's plenty of room for more, especially wrt the
perl modules.
--
Joe Schaef
ing on with his handler's prototype?
IIRC a ($$) prototype will cause modperl to put the handler's
package name in the first argument.
--
Joe Schaefer
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
back to 200 == OK. not only does this make writing
> handlers in perl different than C, but is also creates a problem for
> people who use mod_perl to drive protocols other than HTTP, where 200
> might well mean something entirely different.
+1.
--
Joe Schaefer
--
Reporting bugs: h
Stas Bekman <[EMAIL PROTECTED]> writes:
> If it is implemented already, then it's our *bug* and we just need to
> release Apache-Test with a correct META.yaml.
Either way, this is not a showstopper for apreq.
Here's my +1 for libapreq-1.33.
--
Joe Schaefer
--
without removing the data from the pipeline. If it needs to,
mod_apreq will drive the pipeline to pull more data through,
but the data will remain in the pipeline for later filters/handlers
to see. It's designed this way to allow Apache::Request to be
usable in any pre-response-hand
even if you're familiar with apache2's innards.
The input filter system wasn't really designed
to encourage people to do what you're doing.
So, have you tried using Apache::Request yet?
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
b/perl5/5.8.5/x86_64-linux/auto/DynaLoader/DynaLoader.a: could
> not read symbols: Bad value
I think this means Fedora's DynaLoader.a file needs to be
(re)compiled with -fpic (or -fPIC). Look for "-Duseshrplib"
and/or "cccdlflags='-fPIC'" in perl -V.
--
Joe S
e
currently b0rked, because CPAN thinks mod_perl-2.0.0-RC1
provides it:
% perl -MCPAN -e shell
i /Apache::Test/
...
Module Apache::Test(G/GO/GOZER/mod_perl-2.0.0-RC1.tar.gz)
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://per
ample at
http://perl.apache.org/docs/2.0/user/handlers/filters.html
#Bucket_Brigade_based_Output_Filters
>
If you have problems/questions with the documented
examples, report them and the docs will likely improve.
Best wishes.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
er with
configuration info and error-log output. Maybe it's an apreq
bug, maybe it isn't. But if I can't reproduce your problem
locally, there's not much I can do other than offer you my
sympathy.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail
oria els uploads ja no estan
Try switching the order:
my $table =$mm->param(); #en teoria els uploads ja no estan
my $uploads =$mm->upload();
If that fixes your problem, there's a bug in $mm->upload()
that we need to fix.
--
Joe Schaefer
--
Report pr
te html form look like? Which
browsers (and versions) are you testing?
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
= $req->upload("eps") or
die "Can't locate 'eps' upload";
Also see what happens if you change the form to just a single file
upload, with no other fields.
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Joe Schaefer <[EMAIL PROTECTED]> writes:
> From this, it looks to me like libapreq is parsing the POST data correctly
> (the gif filename showing up as the eps param value is a tell-tale sign that
> the upload was parsed ok). So the now question is: why isn't $mm->upload(
king copy)
@@ -283,6 +283,7 @@
data[len_size] = 0;
SvCUR_set(ST(1), len_size);
SvPOK_only(ST(1));
+SvSETMAGIC(ST(1));
s = apr_brigade_flatten(bb, data, &len_size);
if (s != APR_SUCCESS) {
APREQ_XS_THROW_ERROR(upload, s, "Apache::Upload::slurp",
--
J
"faster CGI.pm"). There are already a few C modules
(mod_spin is a nice example) that use libapreq2. The
upshot is that such modules will all share the *parsed*
POST data, without stealing the *raw* POST data from
other modules.
--
Joe Schaefer
--
Report problems: http://perl.
to address, IMO, has to do with CPAN's
indexing of the Apache:: modules common to both mp1 and mp2 core
distros, because those packages set the underlying apache[12]
architecture. That issue is being debated in a few different forums,
but I think the [EMAIL PROTECTED] list is the best p
n to CPAN?
Please, lets not do that. The reason for Apache2.pm is to support
parallel installation, nothing more. My only gripe with the mp2
release candidates is that I would have liked to see a few production
mp2 releases on CPAN before its mp1 indexing starts to disappear.
--
Joe Sc
Stas Bekman <[EMAIL PROTECTED]> writes:
> Joe Schaefer wrote:
>> My only gripe with the mp2
>> release candidates is that I would have liked to see a few production
>> mp2 releases on CPAN before its mp1 indexing starts to disappear.
>
> Sure, you can ask Andre
p2, or maybe those folks just migrate
wholesale to mp2. Or maybe some enlightened person
will wander in and show us all a demonstrably better
way to handle the CPAN situation. Or maybe I'm wrong,
and the extended itching turns out to be just more
bitching. Who knows?
--
Joe Schaefer
ger, the emacs binary
is ~60% larger (3985408 vs 6633208), but ps reports
almost a four-fold increase in VSZ. Go figure.
Here's a possibly relevant link I found while googling
for an answer:
https://www.redhat.com/archives/amd64-list/2004-September/msg3.html
--
Joe Schaefer
--
y. But nobody sane mangles C
function names by actually embedding version numbers in them; the
linker's toolchain is expected to work that out (with a few hints
here and there).
--
Joe Schaefer
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist
1 - 100 of 274 matches
Mail list logo
