Hey SymbolicFrank,
Yes, but there are a lot of rules they have to conform to for them to be added to the message.
I'm really sorry, you lost me here.
Could you please elaborate on what you call rules and what you call message?
So you have to override multiple methods to be able to see what is sent just before it is. That is the problem.
From the quick look that I gave the code, I think that
TFPHTTPClient is not a complicated HTTP Client.
It does HTTP 1.0 or 1.1 and that's pretty much it. I think it does not do HTTP 2.0, nor does it do compressed or chunked transport. But I could be wrong on these last ones.
It pretty much sends what you can gather from
RequestHeaders,
RequestBody and that's pretty much it, no magic behind the curtain.
So, when you say that you have to override multiple methods, I really don't understand your objective.
Ok, you can check the ResponseHeaders, unless you got something else than a 200.
If I'm not mistaken, apart from some 500 errors, you always get content back on the
ResponseHeaders, so I don't understand your argument here, sorry.
In the end, what I think is that I really don't understand your debugging needs. And that's normal since you actually never specified them. You just stated that you can't debug it.
So please, in the quest to better help you, could you please give more specifics on what you're expectations for the debug are?
Could you provide us with an example of what you input and then what you're expecting to get back on such debug?
This would really help us give you a more precise and focused help.
Cheers,
Gus