From: Geoffrey Young <[EMAIL PROTECTED]>
GY> I didn't think that was what he was asking about. getting the POST
GY> data from the main request in a subrequest is generally easy with
GY> Apache::Request:
Oops, you're right. I was thinking that Mark (jump in any time) needed to keep things
in
> and writable, and are doing an internal redirect, you might be able
> to just reload it:
>
> $STDIN = $r->content; $r->internal_redirect_handler($handler);
>
>
> I know I've done this sort of thing (redirecting POSTs) with a
> session system. That is, a
perl.apache.org/docs/1.0/guide/snippets.html#Redirecting_POST_Requests
I thought I recalled a $STDIN var in mod_perl, but didn't find anything with a quick
scan of the docs. If that var ~is~ available, and writable, and are doing an internal
redirect, you might be able to just reloa
> Presently I get all the incoming parameters via Apache::Request and
> append to the URL before redirecting but this is not ideal as I?d like
> to spit the modified parameters out in a POST. Can anyone give me any
> advice?
see
http://perl.apache.org/docs/1.0/guide/snippets.html#Redirecting
Title: $r->content
I’m trying to read some posted data, modify it and then redirect request inc the modified data. Something like;
my $r = Apache::Request->new(Apache->request);
my %form = $r->content;
#modify %form
$r->content(%form);
$r->internal_redirect_handler($some_
Are you also processing the posted data at some earlier request stage? It
doesn't sound like you would be but I thought I would ask.
Richard
- Original Message -
From: Mike Melillo
To: [EMAIL PROTECTED]
Sent: Tuesday, May 14, 2002 5:22 PM
Subject: $r->args vs $r->content
riginal Message-
From: Issac Goldstand [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 14, 2002
4:39 AM
To: Mike Melillo
Cc: [EMAIL PROTECTED]
Subject: Re: $r->args vs
$r->content
Quoting Mike Melillo
<[EMAIL PROTECTED]>:
>
> Hi,
>
> One of the field
Quoting Mike Melillo <[EMAIL PROTECTED]>:
>
> Hi,
>
> One of the fields is an image file that will be uploaded so I need to
> use POST requests. Is this a job for Apache::Request? The eagle book
> doesn't cover it much because it was "experimental" at the time of
> publishing.
>
There's a v
Yup, slight memory error when responding, sorry :)
$r->content is going to be empty if you're not using the
application/x-www-form-urlencoded, perldoc Apache.
Page 131 of the Eagle book also says
"If the browser uses the newer multiport/form-data encoding (which is
used for
No, It specifies multipart/form-data because page 131 of the eagle says
its used for file uploads.
Mike
-Original Message-
From: Todd Finney [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 13, 2002 11:16 PM
To: [EMAIL PROTECTED]
Subject: Re: $r->args vs $r->content
At 10:29 PM 5
At 10:29 PM 5/13/02, Mike Melillo wrote:
>It works, but if I use the method in the eagle book for POST requests
>%params = $r->content; then nothing gets returned. I've even printed
>%params to the apache errlog with DataDumper, and its empty.
>
>One of the fields is an
for POST requests
%params = $r->content; then nothing gets returned. I've even printed
%params to the apache errlog with DataDumper, and its empty.
One of the fields is an image file that will be uploaded so I need to
use POST requests. Is this a job for Apache::Request? The eagle book
I'm looking to see if anyone can verify whether the following behavior is a
Feature or a Bug. From within a PerlRequestHandler:
my $content = $r->content();
my $cookie = CGI::Cookie->parse( $r->headers_in->get('Cookie') );
works fine, but the
13 matches
Mail list logo
