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

Take follow-redirects config into account for programmatic client created #45492

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Jan 10, 2025

This property (as other config properties) is meant to apply to all clients, including ones created
programmatically.
Users can still override this by using .followRedirects() on the client builder

…ated

This property (as other config properties) is meant
to apply to all clients, including ones created
programmatically.
Users can still override this by using
.followRedirects() on the builder
@geoand
Copy link
Contributor Author

geoand commented Jan 10, 2025

cc @maxandersen who first discovered the issue

Copy link

🎊 PR Preview 6742705 has been successfully built and deployed to https://quarkus-pr-main-45492-preview.surge.sh/version/main/guides/

  • Images of blog posts older than 3 months are not available.
  • Newsletters older than 3 months are not available.

Copy link

quarkus-bot bot commented Jan 10, 2025

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 4f22bf7.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

Copy link

quarkus-bot bot commented Jan 10, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 4f22bf7.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

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

Successfully merging this pull request may close these issues.

1 participant