x-served-by header is being truncated.

[alex8bitw]

What version of Hono are you using?

3.12.8

What runtime/platform is your app running on?

Fastly

What steps can reproduce the bug?

Proxy a request at Fastly, and view headers.

From origin 
172046317ns: Response Header => response: 1, x-served-by: cache-gnv1820032-GNV, cache-gnv1820026-GNV, cache-den8282-DEN, cache-den8282-DEN
172046414ns: Response Header => response: 1, x-cache: MISS, MISS, MISS, MISS

To Client 
174420496ns: Response Header => response: 0, x-served-by: cache-den8282-DEN
174420883ns: Response Header => response: 0, x-cache: MISS, MISS, MISS, MISS

What is the expected behavior?

x-served-by with 5 entries, not 1.

What do you see instead?

Trucnated x-served-by to 1 entry

Additional information

No response

[yusukebe]

Hi @alex8bitw

How can I reproduce this in my local enviroment?