Skip to content

Add follow_location configuration to not follow redirects by default - #51

Merged
cliffano-shn merged 1 commit into
mainfrom
fix/follow-location
Nov 2, 2026
Merged

cliffano-shn merged 1 commit into
mainfrom
fix/follow-location

Conversation

@rJunx

@rJunx rJunx commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

swagger_aem 4.0.x and swagger_aem_osgi 2.0.x always followed redirects, as their API clients used opts[:follow_location] || true, while ruby_aem relies on getting 302 responses back. swagger_aem 4.1.0 and swagger_aem_osgi 2.1.0 don't follow redirects by default and honour follow_location, so ruby_aem now passes it on every API call, configurable via the new follow_location configuration value (default: false).

swagger_aem 4.0.x and swagger_aem_osgi 2.0.x always followed redirects,
as their API clients used `opts[:follow_location] || true`, while
ruby_aem relies on getting 302 responses back. swagger_aem 4.1.0 and
swagger_aem_osgi 2.1.0 don't follow redirects by default and honour
follow_location, so ruby_aem now passes it on every API call, configurable
via the new follow_location configuration value (default: false).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cliffano-shn
cliffano-shn merged commit e609f19 into main Nov 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants