We just started using cntlm v0.92.3 in OS X 10.10.5 recently and just noticed that if we send an HTTP POST through cntlm, cntlm sends out a probe request as an HTTP POST with no body followed by an HTTP POST with the body of the original request, both to the target URL.
This is a problem, not just because of the additional traffic, but it could trigger saves, etc. with data that is not intended by the client. This looks intentional since cntlm actually logs that it is doing this with "Client has a body - forcing second request." Could you explain why you are doing this and whether the probe request is required or something we can turn off?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We just started using cntlm v0.92.3 in OS X 10.10.5 recently and just noticed that if we send an HTTP POST through cntlm, cntlm sends out a probe request as an HTTP POST with no body followed by an HTTP POST with the body of the original request, both to the target URL.
This is a problem, not just because of the additional traffic, but it could trigger saves, etc. with data that is not intended by the client. This looks intentional since cntlm actually logs that it is doing this with "Client has a body - forcing second request." Could you explain why you are doing this and whether the probe request is required or something we can turn off?
Thanks!