"C. Michael Pilato" <cmpil...@gmail.com> writes: > The log message for r2419 mentions "files" larger than 4Gb, and leads me > to believe that this problem only affects GETs. But here, Philip avoids > the term "files" and talks about the "compressed size". Does the bug > fixed in r2419 manifest on any response > 4GB, such as a bulk-mode > REPORT carrying a whole Subversion tree that's larger than 4GB?
I can trigger the decompression error on a 5GB REPORT by setting http-bulk-updates=yes on the client side. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
