fix(storage-s3): validate Content-Length before appending header

[id3er0]

Description

Fixes "Parse Error: Invalid character in Content-Length" errors that occur when S3-compatible storage providers (like MinIO) return undefined or invalid ContentLength values.

Changes

• Added validation before appending Content-Length header in staticHandler.ts
• Only appends Content-Length when value is present and numeric
• Prevents HTTP specification violations from undefined/invalid values

Code Changes

const contentLength = String(object.ContentLength);
if (contentLength && !isNaN(Number(contentLength))) {
  headers.append('Content-Length', contentLength);
}

Issue

• Resolves MinIO compatibility issues where undefined ContentLength causes client parse errors
• Maintains backward compatibility when ContentLength is valid

Testing

• Tested with MinIO provider returning undefined ContentLength
• Verified valid Content-Length values are still properly set
• Confirmed no regression in existing S3 functionality

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published

[github-actions]

🚀 This is included in version v3.53.0