HTTP/2 does not use status message. We recently migrated to new jetty server that uses http2 (https://github.com/prestodb/presto/pull/23356). From native worker, passing status message is no op. In some cases we parse the error message and pick the first line as message. This is not necessary as status message is not used. Proxygen's RequestBuilder::status function expects status message and sets http version 1/1 hard coded. However, after discussing with proxygen folks, found that they intentially set it and proxygen does not depend on this version number, instead they use server next protocol/client next protocol.
Extensive testing is done with shadow tests, also existing e2e tests pass.
HTTP/2 does not use status message. We recently migrated to new jetty server that uses http2 (https://github.com/prestodb/presto/pull/23356). From native worker, passing status message is no op. In some cases we parse the error message and pick the first line as message. This is not necessary as status message is not used. Proxygen's RequestBuilder::status function expects status message and sets http version 1/1 hard coded. However, after discussing with proxygen folks, found that they intentially set it and proxygen does not depend on this version number, instead they use server next protocol/client next protocol.
Extensive testing is done with shadow tests, also existing e2e tests pass.