Another way to proceed at this point, if the connection is not an SSL connection, would be to use Wireshark to log the interaction. Seeing headers is trivial and would tell you everything you need to know without patching the code.
Karl On Mon, Jun 18, 2012 at 8:21 AM, Karl Wright <[email protected]> wrote: > HTTPClient 3.1 itself does not seem to provide a logging option for > logging the body. However, it should be straightforward to add this > to the ManifoldCF code. What version are you running, so that I can > provide the appropriate patch? > > Karl > > > > On Mon, Jun 18, 2012 at 8:09 AM, Jan van Haarst <[email protected]> wrote: >> Hello all, >> >> I'm a colleague of the original poster [1]. >> >> We got a lot further in figuring out the flow of the website, and thus the >> way ManifoldCF should crawl it. >> In that process, we discovered that our problem might lie with >> httpclient ,as the server responds with a 401.2 response, because the client >> doesn't send authentication headers, as mentioned in [2]. >> >> My question is this : >> Is the raw response of the server stored somewhere in case of a 401 return >> code ? >> If so, I can check whether my idea is right, and after that try to fix it. >> >> With kind regards, >> >> Jan van Haarst >> >> [1] >> http://mail-archives.apache.org/mod_mbox/incubator-connectors-user/201205.mbox/%3CCAFxWV0WY_Vojsshbfr0PSs%3DG-Xpd1wUJXFcbVVsOvntbXs1zRg%40mail.gmail.com%3E >> [2] http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/8feeaa51-c634-4de3-bfdc-e922d195a45e.mspx?mfr=true >> >>
