On Wed, Apr 06, 2005 at 04:59:58PM -0500, Gunnar Wolf wrote: > Hmmm... Strangely, that rings another bug on me - a bug I didn't > report as I was unable pin it down and reproduce it - When parsing the > parameters, some of the fields were lost when receiving them via POST, > but it worked fine using POST (it was with this same script I sent > you).
Uhm, no s/POST/GET/ at some point in the middle there? :-) >> To be honest, I'm not sure if this is related or not. The documentation seems >> to demand that you "use Apache::Upload" at the top, though, which seems to >> fix the error for me (but the warning's still there). > Ok, I fixed this (for me) by removing the DISABLE_UPLOADS=>0, as it is > something close to a NOOP :) But... Well, the bug exists :( To me, it sounds like the best thing to do ATM would be taking the bug upstream; it might of course be a bug in my packaging, but it'd have to be rather obscure, I believe :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
