@Leif : 1) TSHttpTxnClientRespBodyBytesGet() is giving the correct content length as opposed to TSHttpTxnServerRespBodyBytesGet() (i don't have any plugin to share right now but this api always gives 0). What difference it will make to use one api over another ? 2) TSHttpTxnServerRespHdrBytesGet() & TSHttpTxnClientRespHdrBytesGet() are giving different values. Can you please let me know what is the difference between the two.
@Brian : yes i want to calculate the response body size at the txn close only. On Fri, Jul 14, 2017 at 9:45 PM, Brian Geffon <[email protected]> wrote: > I'd like to add something to this, you may not be able to calculate the > body size until a TXN Close, if you're trying to get the response body > since in READ_RESPONSE_HEADERS you're probably going to have a bad time > unless a content-length header is set, which even then may not result in > response body bytes being available. (But I also didn't check the code, I'm > just assuming). I'd try again in a TXN Close hook to see if it's available > there. > > Brian > > On Fri, Jul 14, 2017 at 8:57 AM Leif Hedstrom <[email protected]> wrote: > >> >> On Jul 14, 2017, at 1:37 AM, Gaurav Bansal <[email protected]> wrote: >> >> hi all, >> I want to get the total http response size (i.e. size of headers + body). >> For this i tried using below two api's : >> TSHttpTxnServerRespBodyBytesGet(txnp) //always returns 0 >> TSHttpTxnServerRespHdrBytesGet(txnp) //seems to work fine >> >> >> >> >> Hmmm, sounds broken / bad. First I thought it might be cache hit / miss >> related, but then reading your email again, it seems the header bytes is >> always right, so that can’t be it… Do you have a reproducible test case? A >> small plugin that you can maybe attach to a Github Issue? >> >> That much said, maybe you could try these instead? >> >> TSHttpTxnClientRespHdrBytesGet() >> TSHttpTxnClientRespBodyBytesGet() >> >> >> Cheers, >> >> — leif >> >>
