I have seen a different result from svn log and I can cherry pick around and 
see some expected output.


The curl output below has… "~$ployment%20to%20Test.doc">~$ployment to 
Test.doc</  … Could the file with ~$ and %20 cause an issue?


svn  -rr1013 log https://scm-uat.web.att.com:6022/svn/asgard
------------------------------------------------------------------------
r1013 | asgardia | 2015-05-04 15:48:15 -0700 (Mon, 04 May 2015) | 1 line

stuff
------------------------------------------------------------------------
[an2124@hlth509 test3]$ svn  -rr1014 log 
https://scm-uat.web.att.com:6022/svn/asgard
------------------------------------------------------------------------
r1014 | asgardia | 2015-05-08 16:05:07 -0700 (Fri, 08 May 2015) | 1 line

stuff
------------------------------------------------------------------------
[an2124@hlth509 test3]$ svn  -rr1015 log 
https://scm-uat.web.att.com:6022/svn/asgard
svn: E175002: Unexpected HTTP status 400 'Bad Request' on 
'/svn/asgard/!svn/rvr/1015'

svn: E160062: Additional errors:
svn: E160062: Malformed node revision ID string


Not sure how to curl and cherry pick a version but here is latest.


curl -k -u an2124 --insecure https://scm-uat.web.att.com:6022/svn/asgard/

Enter host password for user 'an2124':

<html><head><title>asgard - Revision 1116: /</title></head> <body>  <h2>asgard 
- Revision 1116: /</h2>  <ul>

  <li><a href="../">..</a></li>

  <li><a href=".project">.project</a></li>

  <li><a href="00%20Admin/">00 Admin/</a></li>

  <li><a href="10%20CSCM+SCME%20Documents/">10 CSCM+SCME Documents/</a></li>

  <li><a href="20%20ARCADE%20Documents/">20 ARCADE Documents/</a></li>

  <li><a href="30%20SDT/">30 SDT/</a></li>

  <li><a href="40%20Regression%20Test%20Suite/">40 Regression Test 
Suite/</a></li>

  <li><a href="70%20Miscellaneous/">70 Miscellaneous/</a></li>

  <li><a href="80%20Archive/">80 Archive/</a></li>

  <li><a href="90_Temp/">90_Temp/</a></li>

  <li><a href="ARCADE/">ARCADE/</a></li>

  <li><a href="Arcade/">Arcade/</a></li>

  <li><a href="Asgard">Asgard</a></li>

  <li><a href="CCM06/">CCM06/</a></li>

  <li><a href="CCM06_177/">CCM06_177/</a></li>

  <li><a href="Images/">Images/</a></li>

  <li><a href="Kunebelles">Kunebelles</a></li>

  <li><a href="Misc/">Misc/</a></li>

  <li><a href="Optimizations/">Optimizations/</a></li>

  <li><a href="Scripts/">Scripts/</a></li>

  <li><a href="Selenium%20Stuff/">Selenium Stuff/</a></li>

  <li><a href="Thumbs.db">Thumbs.db</a></li>

  <li><a href="almighty-gab/">almighty-gab/</a></li>

  <li><a href="almighty-only/">almighty-only/</a></li>

  <li><a href="aod/">aod/</a></li>

  <li><a href="ccm06_n1_1_29234/">ccm06_n1_1_29234/</a></li>

  <li><a href="ccm06_n1_2_29234/">ccm06_n1_2_29234/</a></li>

  <li><a href="ccm06_n1_3_29234/">ccm06_n1_3_29234/</a></li>

  <li><a href="ccm06_n1_4_29234/">ccm06_n1_4_29234/</a></li>

  <li><a href="ccm06_n1_5_29234/">ccm06_n1_5_29234/</a></li>

  <li><a href="dev1">dev1</a></li>

  <li><a href="developer1/">developer1/</a></li>

  <li><a href="idemo/">idemo/</a></li>

  <li><a href="logs">logs</a></li>

  <li><a href="logs2">logs2</a></li>

  <li><a href="logz">logz</a></li>

  <li><a href="offshore/">offshore/</a></li>

  <li><a href="onshore/">onshore/</a></li>

  <li><a href="sonar/">sonar/</a></li>

  <li><a href="stash">stash</a></li>

  <li><a href="trunk/">trunk/</a></li>

  <li><a href="viewvc/">viewvc/</a></li>

  <li><a href="viewvc_1.1.22/">viewvc_1.1.22/</a></li>

  <li><a href="x">x</a></li>

  <li><a href="yeahyeah">yeahyeah</a></li>

  <li><a href="~$ployment%20to%20Test.doc">~$ployment to Test.doc</a></li>  
</ul>

</body></html>[an2124@hlth509 test3]$



From: Paul Hammant [mailto:p...@hammant.org]
Sent: Wednesday, February 28, 2018 8:28 AM
To: NOCERA, ANDY <an2...@att.com>
Cc: Andreas Krey <a.k...@gmx.de>; Michael Rohan <mro...@stonepillar.com>; 
users@subversion.apache.org
Subject: Re: E130003: The XML response contains invalid XML - svn co and log 
issue on some repos using https/http

As you work toward a conclusion, Andy, do you think there was a different error 
message that could have driven you to root cause more quickly?

Reply via email to