Skip to content

Conversation

@cstamas
Copy link
Member

@cstamas cstamas commented May 23, 2023

@cstamas cstamas self-assigned this May 23, 2023
@Eh2406
Copy link

Eh2406 commented May 23, 2023

Should this retry handler respect aether.connector.http.retryHandler.count?

@cstamas
Copy link
Member Author

cstamas commented May 23, 2023

Should this retry handler respect aether.connector.http.retryHandler.count?

This pr changes ONLY the fact that now client follows rfc2616 and treats listed methods (put among them) as idempotent.

@cstamas
Copy link
Member Author

cstamas commented May 26, 2023

Latest commit exposes all aspects of retryHandler to users via config (defaults to "standard" handler as before in this PR)

@Eh2406
Copy link

Eh2406 commented May 26, 2023

Under what circumstances would a user want the standard retry handler?

@cstamas
Copy link
Member Author

cstamas commented May 26, 2023

No idea, but presence of these options allows to make resolver work "as before". Just an escape hatch, nothing more.

@cstamas cstamas merged commit 7dfd789 into apache:master Jun 1, 2023
@cstamas cstamas deleted the MRESOLVER-361 branch June 1, 2023 07:17
@gnodet gnodet added this to the 1.9.11 milestone Jun 1, 2023
@jira-importer
Copy link

Resolve #1037

1 similar comment
@jira-importer
Copy link

Resolve #1037

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.

4 participants