> On Jun 10, 2019, at 21:38, Sudheer Vinukonda
> <sudheervinuko...@yahoo.com.invalid> wrote:
>
> Can you describe the use cases for needing this API?
>
> Also, why can’t the caller normalise the url returned by
> TSHttpTxnEffectiveUrlStringGet()? It appears like an “overload” to support an
> API just for normalisation alone, unless I’m missing something.
I agree, overloading basic computation into compound APIs is just making things
harder to use, not easier. One could also produce this string from the URL
object I think, and do whatever normalization necessary there.
Let’s hear what the use case is though.
— Leif
>
> - Sudheer
>
>> On Jun 10, 2019, at 6:26 PM, Walt Karas <wka...@verizonmedia.com.invalid>
>> wrote:
>>
>> TSHttpTxnEffectiveUrlStringGet
>
