search

gematik / epa-deployment

Project includes docker-compose file to start all relevant services (including VAU encryption/decryption) for an ePA environment.
Apache License 2.0
11 stars 4 forks source link

VAU Response from medication-render-service #9

Closed ruiyan-yu closed 5 months ago

ruiyan-yu commented 5 months ago

Hi,

I can retrieve the PDF from the medication-render-service using the curl command without any issues.

However, When I send the request via VAU, I receive a response which can be decrypted (HTTP 200 inner), but the content-length does not match the actual payload size. The payload is larger. As a result, the PDF is corrupted and cannot be opened because it's incomplete. Even after manually extracting the bytes with the actual length and writing them to a file, the PDF still can't be opened.

It seems to be an encoding problem. Is anyone else experiencing this issue?

diff_hex_header.zip pdfs.zip

fnoGematik commented 5 months ago

Hey @ruiyan-yu,

I'll try to reproduce this issue locally.

Anyway. Could you please try to get the PDF from medication-render-service without using VAU De-/encryption. To do so, send the request to http://:8085/epa/medication/render/v1/eml/pdf.

Best regards,

ruiyan-yu commented 5 months ago

Hi @fnoGematik ,

Thank you! The PDF file (eml.pdf) can be found in the pdfs.zip archive attached to my first post.

fnoGematik commented 5 months ago

Hey @ruiyan-yu,

yesterday I found an issue with an unnecessary type conversion in vau-proxy-server and I was able to reproduce the behavior you described ( Header Content-Lenght was different to the payload size and the payload was not the same as the origin. I already have a fix. I hope we can updated this repository a.s.a.p..

Best regards,

fnoGematik commented 5 months ago

Hey @ruiyan-yu,

we have just released a new version of the vau-proxy-server which contains the fix. If it is possible for you, you are welcome to check whether the fix also solves your problem. All you have to do is update the version of the vau-proxy-server to 1.0.5, which is already published on DockerHub, in the dc-mocks.yaml file. Your feedback is welcome.

Best regards,

sonerd commented 5 months ago

Hey @ruiyan-yu,

we have just released a new version of this deployment project. This includes the fix for your problem. Please give it a try.

Thanks.

ruiyan-yu commented 5 months ago

Hi,

It's working perfectly! Thank you for the hotfix and for setting up the new entitlement service. :)

Best regards