I'm not sure I understand what you're asking... Apache, on it's own, does not support any internal parsing of POST data, multipart or otherwise, so why should mod_perl? For this, we have the Apache::Request library in mod_perl (Which is the mod_perl interface to the libapreq library for Apache's C API). libapreq supports multipart/form-data, even without a file upload...
Issac Vuillemot, Ward W wrote: >All, > >I am still trying to figure out why my setup of mod_perl does not have >multipart POSTs. I rebooted my machine, and found that, whereas I reported >before mod_perl would try to reload the page (which it should not but send >out a text/plain attachment for download), it appears the script (running as >a perl handler) does not see any of the multipart POST. Vanilla posts are >not a problem, though. Even if the information being sent via multipart is >_not_ a file to upload to the server, the information is lost in transit. > >Here is what is odd. > >The same scripts/modules unmodified and running as perl_cgi are okay. >Multipart forms allow me to upload files, et cetera. In short, I am >confident the problem is not with my programming. > >I am using the code snippet, POST2GET, to capture the one-time read of POST >and storing as if it was retrieved via GET. > >Any ideas how to debug this? > >I REALLY REALLY would love some feedback. I would love to think that all my >effort to stay away from M$ ASP are worth it -- esp. when I stand up to >defend Perl, Apache, and mod_perl in an environment that is decidely >M$-bent. > >Thanks! >Ward >
