> -----Ursprüngliche Nachricht----- > Von: Brandon Fosdick > > At this point I'm not sure if I should bother trying the > large file hack for 2.0.55 or just start migrating to 2.2.x. > This no longer seems to be a large file problem, but I'm not > sure what kind of problem it is. Judging by the mod_security > audit log, the client doesn't appear to be doing anything > odd. That is, it's just issuing a LOCK and a PUT for each > file upload. Naturally, my own code is suspect as well, but > it never sees anything bigger than 64K, and it can handle > larger files when I haven't taken half the RAM out. > > I'm stumped.
Have you checked if you can write the files with the default mod_dav_fs provider to the disk? Maybe this is a pool issue in your provider. Pool issue can cause large memory grows. Regards Rüdiger
