Answer myself just for sharing.
I came to know the reason is in that,
in the log report response,there was a ascii backspace(0x08) in the file
name for one <S:added-path> element,.
although I had no idea why and how the backspace could be there.
On Sun, Nov 24, 2013 at 11:35 PM, Chang Chao <charleschung.cn_at_gmail.com>wrote:
> when I click show log on my client pc(192.168.100.101),the "the report
> response contains invalid XML(200 OK)" showed,and log cannot be seen.
> After a little look into the problem through packet capturing,
> I found that the client closed the tcp(HTTP) connection by sending RST
> (see TSVN_showLog.pcapng No.117) while the server(192.168.100.10 http)
> is sending the REPORT response.It seems that some exceptions happend
> in the client.(see TSVN_debugOutput.txt).
> I tried with SVNKit to do the same thing,I got the requested log safe
> and sound.(see SVNKit_showLog.pcapng)
> So I think the problem may lie in the TortoiseSVN (in parsing XML?).
> Although I changed to repo to use svn://server instead of
> http://server,the client worked.
> Any research on why the problem happened is greatly appreciated.
> Here is my TortoiseSVN information.
> TortoiseSVN 1.8.3, Build 24901 - 32 Bit , 2013/10/27 15:38:41
> Subversion 1.8.4, -release
> apr 1.4.8
> apr-util 1.5.2
> serf 1.3.2
> OpenSSL 1.0.1e 11 Feb 2013
> zlib 1.2.8
> BTW,to simplify things,I set "Default number of log messages" to 1.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-11-25 11:27:47 CET