Skip to content

Updated POST data/buckets not passed beyond ModPorter #19

Open
yostinso opened this Issue Jul 1, 2010 · 0 comments

1 participant

@yostinso
yostinso commented Jul 1, 2010

I'm trying to use ModPorter with 2.2.9-10+lenny7 and Rails 2.1.0.

Everything seems to be configured on the Apache side of things (I see the ModPorter debugging output if I compile with rake build_debug), but on the Rails side of things, HTTP_X_UPLOAD is not populated, and the RAW_POST_DATA remains the same -- except that it's truncated. Content-Length and Content-Type are getting updated fine.

I spent most of a day trying to debug this, and finally became discouraged when I discovered that inserting:

apr_off_t *len;
char *buf;
apr_brigade_pflatten(bb, &buf, &len, f->r->pool);
PORTER_LOG("Flattened buffer:");
PORTER_LOG(buf);

right after the apr_brigade_destroy in porter_input_filter output the expected url-encoded string, but the POST data was still the same according to Rails.

Is there an issue with the brigade not being passed on? How else could Rails be getting hold of the original POST data? Is ModPorter passing along the brigade in a nonstandard way? (I note that the tutorials I found use ap_pass_brigade, which isn't used in ModPorter.) In any case, this seems like a ModPorter problem, rather than one of configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.