René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Choosing Whether to Enable Retries in Firebase App Options","articleBody":"Hello,\nI have learned that FCM automatically retries when a 503 response is received.\nHowever, our service already handles retries for undelivered messages through scheduling, so we do not want to use the default retry strategy.\n```\npublic static HttpRequestFactory newAuthorizedRequestFactory(\n\tFirebaseApp app, @Nullable RetryConfig retryConfig) {\n\tHttpTransport transport = app.getOptions().getHttpTransport();\n\treturn transport.createRequestFactory(new FirebaseRequestInitializer(app, retryConfig));\n}\n```\nTo disable this behavior, I attempted to use a method provided in the ApiClientUtils class.\nHowever, after debugging the initialization process, I found that it is not possible to set a custom RetryConfig value.\n\nI assume there is a valid reason for restricting the redefinition of RetryConfig.\nFor example, it may be to prevent retries for responses other than 5xx errors or to avoid excessive retry requests within a short period.\n\nWhat I would like is the ability to **enable or disable the retry feature as needed.**\nI will proceed with creating a PR for this.","author":{"url":"https://github.com/ksiisk99","@type":"Person","name":"ksiisk99"},"datePublished":"2025-02-12T16:55:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/1075/firebase-admin-java/issues/1075"}