Once an upload is finished, mod_porter streams the contents into a new file, which is passed along to the app server. With large files this process can take a long time, and clients, such as swf_upload, can time out waiting for the request to complete.

I am getting "apache 1.3 configuration directives found" whenever I put "Porter On" into my . My Rake ran without any problem when installing the mod_porter into apache, so I am not sure what the problem may be. Can you please shed some lights?

the file was saved successfully by mod porter, but the file still goes into Rack as one of the params, is that to expected? On my dev machine, a 5M file upload takes at least 300ms, which is really slow. Can you shed some lights?

I have my upload form set up to use the iframe redirect hack to simulate an AJAX upload. When modporter is enabled, it downloads the entire file correctly, but when it hands it back to rails, the file created is zero length and the "render :update" code does not get to the browser.

I assume that the "render :update" is getting sent to mod_porter rather than the browser since mod_porter is acting as a middle man. (?)

If you need the code being used, let me know.

A non-modporter upload returns a file object that has .length. ModPorter has .size ; however, to make things smooth also provide a .length.

Rake task only looks for apxs executable; however, on my install ( Ubuntu server 7.10 ) I had only a apxs2 executable. Therefore, I had to make a symbolic link for apxs.

A note about my system: i'm running snow leopard.

When mod_porter is off, my rails app receives RackMultiPart just fine.

When enabling mod_porter (and the rails plugin). I get an object that looks like this in my params hash:

<ModPorter::UploadedFile:0x10407c3a8 @content_type="application/octet-stream", @original_filename="Argentina.gif", @path="/tmp/apreqxlq8oj">

which all seems great- except there is no file in /tmp named apreqxlq8oj

any ideas/advice? /tmp is definitely chmod 777

thanks!