That would be strange for me as far as it looks for Accept-Encoding: gzip
header
I've checked current day:
bash-3.2$ cat access_log.2010-03-10 |grep TortoiseSVN-1.5 |wc -l
1077
I revieved some of them and most of them have resp code
200 or 207
207 Multi-Status (WebDAV) (RFC 4918)
There is also
Do a checkout or command using a SVN client that does not have deflate
support. For example, the TortoiseSVN 1.5.x clients. As soon as you
do this, your server will probably crash.
When the SVN clients have deflate support it all works great. The bug
happens when a client without support hits t
On Tue, Mar 09, 2010 at 05:33:34PM +0100, Stefan Sperling wrote:
> On Tue, Mar 09, 2010 at 05:10:11PM +0100, Leszek Szarlej wrote:
> > Thanks for the info.
> > >See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
> > In mentioned example apache runs on worker mpm. I've sent a message to this
> >
On Tue, Mar 09, 2010 at 05:10:11PM +0100, Leszek Szarlej wrote:
> Thanks for the info.
> >See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
> In mentioned example apache runs on worker mpm. I've sent a message to this
> group few days ago about users experience with svn and worker mpm. I didn't
Thanks for the info.
>See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
In mentioned example apache runs on worker mpm. I've sent a message to this
group few days ago about users experience with svn and worker mpm. I didn't
get any answer. It concerns me if svn is thread-safe and if the said me
On Tue, Mar 09, 2010 at 04:03:33AM +0100, Leszek Szarlej wrote:
> Hi
>
> In svn book ver. 1.0 there is written:
> "Deflate compression places a small burden on the client and server to
> compress and decompress network transmissions as a way to minimize the size
> of the actual transmission. In ca
