There are a few dark nooks and crannies within the code, some of which are complicated enough that they really need illuminating. While sent headers somewhat fall under the purview of private, non-API code, knowing exactly what is being sent when is very valuable. Having this information would allow me to simplify certain test cases, as well as have a greater degree of confidence that the code is operating correctly.
As options are now being passed along on all of the http_* methods, passing an option called {sent_headers: true} along with would likely be convenient enough. This should short the execution -- i.e., it should probably grab the complete header list, but not actually execute the request. Or maybe it executes the request, but just returns the sent headers. I dunno: my brain is mush right now.
There are a few dark nooks and crannies within the code, some of which are complicated enough that they really need illuminating. While sent headers somewhat fall under the purview of private, non-API code, knowing exactly what is being sent when is very valuable. Having this information would allow me to simplify certain test cases, as well as have a greater degree of confidence that the code is operating correctly.
As options are now being passed along on all of the
http_*methods, passing an option called{sent_headers: true}along with would likely be convenient enough. This should short the execution -- i.e., it should probably grab the complete header list, but not actually execute the request. Or maybe it executes the request, but just returns the sent headers. I dunno: my brain is mush right now.