MIGRATION ISSUE: Proxy usage
Pre-Migration Checklist
- [x] I've read the Migration Guide.
- [x] I've reviewed the upgrading notes and major version differences mentioned in
UPGRADING.md. - [x] I've checked AWS Forums and StackOverflow for similar migration issues.
Which JavaScript Runtime is this issue in?
Node.js (includes AWS Lambda)
AWS Lambda Usage
- [ ] Yes, my application is running on AWS Lambda.
- [x] No, my application is not running on AWS Lambda.
Describe the Migration Issue
We are using the @aws-sdk/s3-request-presigner package to generate pre-signed URLs for uploading and downloading objects from S3. When used publicly (without a proxy), everything works as expected. However, when routing traffic through a proxy, the operations fail, and I'm unable to generate or use the pre-signed URLs properly.
How can we configure this to work correctly when using a proxy? Can you help with this?
Code Comparison
No response
Observed Differences/Errors
Additional Context
No response
Hi @JQuarticx - thanks for reaching out.
In order for us to provide guidance, can you share your code snippet and error log? That would help us identify the issue and find the root cause.
This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.
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.