# ktor

Sebastian Kazenbroot-Guppy

05/18/2021, 7:08 PM
Hey folks, I'm using Ktor with Heroku and I'm seeing a problem where because Ktor uses
HTTP/1.1 200
in the response header instead of
HTTP/1.1 200 OK
, Heroku flips out and gives me this
Copy code
http_error="Bad chunk" at=error code=H17 desc="Poorly formatted HTTP response" method=GET path="/scripts" host=<|> request_id=57732c4e-618a-4226-8a1b-5c3c2177faec fwd="" dyno=web.1 connect=0ms service=212ms status=503 bytes= protocol=https
And when you look into error H17 in the Heroku docs, it says specifically that
HTTP/1.1 200 OK
is required, very much including the
. Now this is pretty bogus behaviour from Heroku, I agree, but I don't see any way to get around this through the various Ktor APIs and libraries, is there a path to making Heroku happy? I've made a ticket to track this issue as even if it's not really on Ktor, I expect this will come up for other folks that don't know what's going on down the line.

Aleksei Tirman [JB]

05/19/2021, 8:48 AM
I've replied in a comment of the issue.