You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click the recording's menu, then Download recording
This used to work and result in the recording .jfr and .metadata.json being downloaded to the client. At some point recently this broke - the .metadata.json still appears (since it is actually generated on the client side rather than downloaded from the server), but the request to download the recording file from the S3 provider (cryostat-storage/SeaweedFS in this case) fails with an HTTP 403 Forbidden and a response body indicating that the request signature did not match.
I suspect this has to do with how I put together the external storage URL handling for the case where storage is behind a proxy. The presigned request signature includes information about the host it is valid for, so using a proxy's hostname will fail the signature check.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
I tried running the smoketest with an older storage container image and the behaviour was the same. Nothing else has changed in a while so I'm not sure what is happening. The only other difference is I'm running this on my laptop instead of my desktop - it would be strange if that was the cause but I will test again on my desktop later on.
Current Behavior
./smoketest.bash -gt
localhost:0
oneThis used to work and result in the recording
.jfr
and.metadata.json
being downloaded to the client. At some point recently this broke - the.metadata.json
still appears (since it is actually generated on the client side rather than downloaded from the server), but the request to download the recording file from the S3 provider (cryostat-storage
/SeaweedFS in this case) fails with an HTTP 403 Forbidden and a response body indicating that the request signature did not match.I suspect this has to do with how I put together the external storage URL handling for the case where storage is behind a proxy. The presigned request signature includes information about the host it is valid for, so using a proxy's hostname will fail the signature check.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: