[Bug]: content-type is not being set for jpeg files in HandoverDocumentation

[KoenigMaurice]

Contact Details

maurice.koenig@outlook.com

Describe the bug

When retrieving a jpeg attachment for HandoverDocumentation V1.2 the content-type in the response headers is not set:

When retrieving a pdf attachment the content-type is set

To reproduce

1. Download test AAS
2. Run aaspe server using this test AAS TEST_AAS.zip
3. Download jpg file using http://localhost:5001/submodels/aHR0cHM6Ly9leGFtcGxlLmNvbS9pZHMvc20vMTAyM18zMTEyXzUwNTJfNzUyNw/submodel-elements/Document_01.DocumentVersion_01.DigitalFile_01/attachment
4. Check headers
5. Download pdf file using http://localhost:5001/submodels/aHR0cHM6Ly9leGFtcGxlLmNvbS9pZHMvc20vMTAyM18zMTEyXzUwNTJfNzUyNw/submodel-elements/Document_02.DocumentVersion_01.DigitalFile_01/attachment
6. Check headers

Expected Behaviour

The headers should be set based on the content type specified in the digital file of the shell

Version

adminshellio/aasx-server-blazor-for-demo:main
sha256:f277fa34852bbf595fddb9f764a31ed272e327421a7a5e236970762143e6d104

Operating System

Docker using Windows 10 and WSL