Mailing List Archive: ModPerl: ModPerl

[libapreq2] Should there be two temp (spool) files?

Index | Next | Previous | View Threaded

ryan at livesite

Sep 24, 2008, 11:03 AM

Post #1 of 5 (411 views)
Permalink

[libapreq2] Should there be two temp (spool) files?

When I post a multipart-form request I see two files being written
in my temp directory:

-rw------- 1 ryan users 8318656 2008-09-24 10:51 apreqK5Oiyc
-rw------- 1 ryan users 8318484 2008-09-24 10:51 apreqQ1qs6C

And:

Apache2::Request->new($r)->upload('file')->tempname()

indicates the spool file is "apreqQ1qs6C".

So I wonder what the file "apreqK5Oiyc" is all about. I imagine it is
used to verify the bytes written and is just standard operating
procedure, but I want to ensure I have not created this situation.

Thanks and Cheers,
-Ryan

joe_schaefer at yahoo

Sep 24, 2008, 11:08 AM

Post #2 of 5 (394 views)
Permalink

Re: [libapreq2] Should there be two temp (spool) files? [In reply to]

--- On Wed, 9/24/08, Ryan Gies <ryan[at]livesite.net> wrote:

> When I post a multipart-form request I see two files being
> written
> in my temp directory:
>
> -rw------- 1 ryan users 8318656 2008-09-24 10:51
> apreqK5Oiyc
> -rw------- 1 ryan users 8318484 2008-09-24 10:51
> apreqQ1qs6C
>
> And:
>
>
> Apache2::Request->new($r)->upload('file')->tempname()
>
> indicates the spool file is "apreqQ1qs6C".
>
> So I wonder what the file "apreqK5Oiyc" is all
> about.

It's spooling the contents of the raw (unparsed) body.
You can tell apreq not to do this by calling $r->discard_request_body
in your handler after invoking Apache2::Request::new.

ryan at livesite

Sep 24, 2008, 12:00 PM

Post #3 of 5 (393 views)
Permalink

Re: [libapreq2] Should there be two temp (spool) files? [In reply to]

On Wed, 24 Sep 2008 11:08:24 -0700 (PDT)
Joe wrote:

> It's spooling the contents of the raw (unparsed) body.
> You can tell apreq not to do this by calling $r->discard_request_body
> in your handler after invoking Apache2::Request::new.

When discarding the request body, I receive the error:

End of file found

(which happens when APR_BUCKET_IS_EOS). I can see the spool file being
written and *presume* the multi-part boundary is missing. In a
PerlHeaderParserHandler I am executing:

1) Apache2::Request->new()
2) $r->add_input_filter()
3) $r->discard_request_body()

Swapping steps 2 & 3 will yield same error. If calling
$r->discard_request_body() like this is not commonly known to work maybe
I should follow-up with the libapreq2 development list? If this is
known to work then obviously I need to isolate error.

joe_schaefer at yahoo

Sep 24, 2008, 12:07 PM

Post #4 of 5 (393 views)
Permalink

Re: [libapreq2] Should there be two temp (spool) files? [In reply to]

--- On Wed, 9/24/08, Ryan Gies <ryan[at]livesite.net> wrote:

> When discarding the request body, I receive the error:
>
> End of file found
>
> (which happens when APR_BUCKET_IS_EOS). I can see the
> spool file being
> written and *presume* the multi-part boundary is missing.
> In a
> PerlHeaderParserHandler I am executing:
>
> 1) Apache2::Request->new()
> 2) $r->add_input_filter()
> 3) $r->discard_request_body()

Why are you doing step 2? You shouldn't need to add an
input filter for apreq to work.

> Swapping steps 2 & 3 will yield same error.

> If calling
> $r->discard_request_body() like this is not commonly
> known to work maybe
> I should follow-up with the libapreq2 development list? If
> this is
> known to work then obviously I need to isolate error.

It's known to work for a few people, but it's not the default
behavior. If you can't decipher why it's not working for you
then asking on apreq-dev@ makes sense.

ryan at livesite

Sep 24, 2008, 12:18 PM

Post #5 of 5 (391 views)
Permalink

Re: [libapreq2] Should there be two temp (spool) files? [In reply to]

On Wed, 24 Sep 2008 12:07:23 -0700 (PDT)
Joe wrote:

> > 1) Apache2::Request->new()
> > 2) $r->add_input_filter()
> > 3) $r->discard_request_body()
>
> Why are you doing step 2? You shouldn't need to add an
> input filter for apreq to work.

Step 2 is Apache2::UploadProgress::track_progress

> It's known to work for a few people, but it's not the default
> behavior. If you can't decipher why it's not working for you
> then asking on apreq-dev@ makes sense.

I will try to reproduce the issue with a simple test case and follow up
there if necessary. Thank you.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com