Steinar H. Gunderson dijo [Wed, Apr 06, 2005 at 10:40:02PM +0200]: > I've looked a bit into this. First, latest SVN snapshot doesn't work (ie. > gives the same warning, and then immediately segfaults :-) ), so there is no > immediately known fix. Second, I don't really understand what's happening > here; it looks like the "parser" in question is something that's supposed to > be derived from the "content type" of the "environment"; it _might_ be that > the idea here is to have separate parsers depending on whatever the user > sends in. (In that case, it's logical that it can't find a parser on a GET, > since it doesn't contain a payload.)
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). > > - The error happens in the _process_upload function, precisely at the > > first mention of $req->upload, which should return an empty hashref > > if no upload was received: > > return $upload unless $req->upload; > > 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 :( -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5554-9450 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
