Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix 403 error from AWS when sending a signed request #205

Merged
merged 1 commit into from Jul 30, 2018

Conversation

rochdev
Copy link
Member

@rochdev rochdev commented Jul 30, 2018

This PR fixes 403 errors from AWS when sending signed requests.

AWS uses the headers when signing, and since we are altering the headers when injecting the span context, the signature would become invalid. This is unnecessary for requests to AWS since it cannot propagate context, so this PR removes the injection for these requests.

@rochdev rochdev added bug Something isn't working integrations labels Jul 30, 2018
@rochdev rochdev added this to the 0.5.3 milestone Jul 30, 2018
@rochdev rochdev merged commit 4dc670f into master Jul 30, 2018
@rochdev rochdev deleted the fix-aws-signature branch July 30, 2018 18:29
tlhunter added a commit that referenced this pull request Nov 15, 2023
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
tlhunter added a commit that referenced this pull request Nov 15, 2023
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
pull bot pushed a commit to astradot/dd-trace-js that referenced this pull request Nov 15, 2023
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts DataDog#205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes DataDog#3719
khanayan123 pushed a commit that referenced this pull request Jan 2, 2024
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
khanayan123 pushed a commit that referenced this pull request Jan 2, 2024
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
khanayan123 pushed a commit that referenced this pull request Jan 2, 2024
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
khanayan123 pushed a commit that referenced this pull request Jan 2, 2024
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
khanayan123 pushed a commit that referenced this pull request Jan 2, 2024
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
khanayan123 pushed a commit that referenced this pull request Jan 2, 2024
- removes the code that disabled tracing headers when amazon signature headers were present
- essentially reverts #205
- was originally done to prevent breaking AWS signatures
- apparently the presence of our headers does not break amazon signatures after all
- fixes #3719
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working integrations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants