Describe the bug
In Debian 12 Distroless images, the mime.TypeByExtension(".tif") function in Golang is returning an empty string, indicating that the MIME type for .tif files is not being recognized. This behavior is inconsistent with other environments where the function correctly returns the MIME type for .tif files.
To Reproduce
Steps to reproduce the behavior:
Use a Docker container with Debian 12 Distroless image.
Run a Golang application that includes the mime.TypeByExtension(".tif") function.
Observe the output, noting that the function returns an empty string instead of the expected MIME type for .tif files.
Expected behavior
The expected behavior is for mime.TypeByExtension(".tif") to return the correct MIME type for .tif files, as it does in other environments.
Additional context
This issue is critical for applications that rely on MIME type detection, particularly for processing .tif files. It seems to be specific to Debian 12 Distroless images, as the same code functions correctly in other environments. Any insights or solutions to resolve this inconsistency would be greatly appreciated.
Describe the bug In Debian 12 Distroless images, the mime.TypeByExtension(".tif") function in Golang is returning an empty string, indicating that the MIME type for .tif files is not being recognized. This behavior is inconsistent with other environments where the function correctly returns the MIME type for .tif files.
To Reproduce Steps to reproduce the behavior:
Use a Docker container with Debian 12 Distroless image. Run a Golang application that includes the mime.TypeByExtension(".tif") function. Observe the output, noting that the function returns an empty string instead of the expected MIME type for .tif files.
Expected behavior The expected behavior is for mime.TypeByExtension(".tif") to return the correct MIME type for .tif files, as it does in other environments.
Additional context This issue is critical for applications that rely on MIME type detection, particularly for processing .tif files. It seems to be specific to Debian 12 Distroless images, as the same code functions correctly in other environments. Any insights or solutions to resolve this inconsistency would be greatly appreciated.