Expose HTTP response headers in websocket upgrade request

[esauerbo]

Describe the feature

It would be helpful to have access to the response headers in the initial http upgrade request for a websocket connection. We are specifically looking to access the date. From the below screenshots you can see the headers in the network tab but not when logging the response.

Use Case

The Amplify UI Face Liveness Detector provides a UI component for Amazon Rekognition Face Liveness using the client-rekognitionstreaming package. Some customers are getting Invalid Signature Exceptions due to clock skew issues.

We want to fix this by catching these exceptions and attempting to restart the session with a systemClockOffset that's the difference between device and server time. This has been implemented on the android liveness component, but currently isn't possible in web because we cannot access the http upgrade headers.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

V3

Environment details (OS name and version, etc.)

any

[kuhe]

there doesn't seem to be a way to retrieve upgrade response headers in a browser using the WebSocket class.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.