HEAD request return 404 while GET returns 200

Summary

I have a script that checks for a certain release to be available, this today "hung forever" because HEAD request are answered as 404.

Steps to reproduce

curl -s -o /dev/null --head -w "%{http_code}" https://projects.eclipse.org/projects/technology.tycho/releases/4.0.8

returns 404

curl -s -o /dev/null --get -w "%{http_code}" https://projects.eclipse.org/projects/technology.tycho/releases/4.0.8

returns 200

What is the current bug behavior?

HEAD should not return 404 when the page exits.

What is the expected correct behavior?

200 code is returned instead

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Any techniques that uses a HEAD to only get the response headers will yield wrong results.