fix: wildcard head return content-length header

[climba03003]

Fixes #447

The reason behind we should not use exposeHeadRoute is that inside pumpSendToReply, we never provide payload for HEAD route. So, fastify think it is providing empty response and override the Content-Length unexpectedly.

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[gurgunday]

Haha, you are fast ;)

Thanks for the PR, you are right

[gurgunday]

lgtm

[gurgunday]

Can you release a patch?

[climba03003]

Can you release a patch?

I can, but most of the time I will wait for two approval before merge.

[gurgunday]

Why? There weren't unfinished test errors before?

[climba03003]

Because we no longer have GET and HEAD registered separately.
FYI: The internal HEAD route also trigger onRoute hook.

[gurgunday]

@climba03003 this looks like a problem in Fastify too, no? A HEAD route (that's linked to a GET route) should automatically calculate and send the header Content-Length while stripping the body IMO

What do you think?

[climba03003]

this looks like a problem in Fastify too, no?

No, as described in the PR @fastify/static are sending empty string or undefined in HEAD route.
So, the core imagine you sending nothing and correct the Content-Length.

The automatic one requires to always send the actual payload otherwise it can not calculate properly.

[gurgunday]

Okay, thanks