Skip to content

fix: 4xx-handling-when-on-proxy #262

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

Merged
merged 6 commits into from
Apr 8, 2025
Merged

Conversation

polbins
Copy link
Contributor

@polbins polbins commented Apr 3, 2025

Summary

We now treat 400 errors differently based on responses that might be returned when connected to a proxy. In this PR we opted to use the eventsToDrop as an indicator if the response is coming from Amplitude BE (meaning it includes the required invalid fields), or if it's from a proxy.

Checklist

  • Does your PR title have the correct title format?
  • Does your PR have a breaking change?:

@polbins polbins requested a review from igor-amp April 3, 2025 21:21
@polbins polbins marked this pull request as draft April 3, 2025 21:24
@polbins polbins force-pushed the AMP-127313/4xx-handling-when-on-proxy branch from 665c99b to a6dcbc0 Compare April 3, 2025 21:55
@polbins polbins marked this pull request as ready for review April 3, 2025 22:57
Copy link
Contributor

@igor-amp igor-amp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

- this prevents changing the order of events when this scenario happens
@polbins polbins merged commit 7561305 into main Apr 8, 2025
4 checks passed
@polbins polbins deleted the AMP-127313/4xx-handling-when-on-proxy branch April 8, 2025 02:40
github-actions bot pushed a commit that referenced this pull request Apr 9, 2025
## [1.20.6](v1.20.5...v1.20.6) (2025-04-09)

### Bug Fixes

* 4xx-handling-when-on-proxy ([#262](#262)) ([7561305](7561305))
Copy link

github-actions bot commented Apr 9, 2025

🎉 This PR is included in version 1.20.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants