Fix 403 error in load_features() by adding proper User-Agent header #62
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
load_features()method on self-hosted GrowthBook instancesGrowthBook-Python-SDK/{version}formatProblem
The Python SDK was failing with 403 errors when calling
load_features()becauseurllib3.PoolManager()sends minimalheaders by default. Some servers (particularly self-hosted GrowthBook instances with WAF/nginx protection) block
requests without proper User-Agent headers.
Solution
Modified the
_get()method inFeatureRepositoryclass to include a proper User-Agent header for all HTTP requests.Testing
load_features()now works on self-hosted instancesImpact