? xdocs/.cookies.xml.swp ? xdocs/.navigation.xml.swp ? xdocs/.troubleshooting.xml.swp ? xdocs/auth.patch ? xdocs/cookies.xml ? xdocs/threading.patch Index: xdocs/navigation.xml =================================================================== RCS file: /home/cvspublic/jakarta-commons/httpclient/xdocs/navigation.xml,v retrieving revision 1.6 diff -u -r1.6 navigation.xml --- xdocs/navigation.xml 26 May 2003 15:13:43 -0000 1.6 +++ xdocs/navigation.xml 28 May 2003 10:52:55 -0000 @@ -19,6 +19,7 @@ + Index: xdocs/troubleshooting.xml =================================================================== RCS file: /home/cvspublic/jakarta-commons/httpclient/xdocs/troubleshooting.xml,v retrieving revision 1.2 diff -u -r1.2 troubleshooting.xml --- xdocs/troubleshooting.xml 11 Mar 2003 08:03:12 -0000 1.2 +++ xdocs/troubleshooting.xml 28 May 2003 10:52:56 -0000 @@ -56,17 +56,15 @@

If you've tried the things above and still can't work out how to fix the problem, it might be time to contact the mailing lists for support. Which list to - contact depends on exactly where you think the problem lies. If you - think you've just got an error in your code somewhere, probably the - commons-user list is the best place, but if you think that HttpClient is - at fault, the commons-httpclient-dev list is probably a better choice.

- -

Please do not cross-post to both lists.

+ href="mail-lists.html">mailing list for support. All questions, bug + reports etc should be directed to the HttpClient development list as all + the really knowledgeable people for HttpClient are there and most are not + also on the commons-user list.

When you do send off the email, please include as much detail as you - can, including attaching wire trace logs if you think they'll help (they - often do). If you are seeing exceptions being thrown the full stack + can, particularly including attaching wire trace logs as there is almost + nothing we can do to help without them. + If you are seeing exceptions being thrown the full stack trace is essential to tracking down the problem. Any of the information you gained from the "things to try" section above are probably worth mentioning.