Major Description
Currently, the ordering of API hooks is:
txn_start -> [receive headers from client] -> pre_remap -> remap -> read_request -> os_dns_lookup
This should be ordered differently:
txn_start -> [receive headers from client] -> read_request -> pre_remap -> remap -> post_remap -> os_dns_lookup
This would involve adding a post_remap API hook and re-arranged the SM ordering of hooks to more closely match what you would expect.