Skip to content

feat: support independent response time route setting #3981

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

Open
wants to merge 5 commits into
base: v3.x.x
Choose a base branch
from

Conversation

pablocarle
Copy link
Contributor

@pablocarle pablocarle commented Feb 5, 2025

Description

According to Spring Cloud Gateway documentation, there are two timeout route settings, both could be set externally:
https://docs.spring.io/spring-cloud-gateway/reference/spring-cloud-gateway/http-timeouts-configuration.html
https://docs.spring.io/spring-cloud-gateway/reference/appendix.html#page-title

Type of change

  • feat: New feature (non-breaking change which adds functionality)

Checklist:

  • My code follows the style guidelines of this project
  • PR title conforms to commit message guideline ## Commit Message Structure Guideline
  • I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • The java tests in the area I was working on leverage @nested annotations
  • Any dependent changes have been merged and published in downstream modules

Copy link

sonarqubecloud bot commented Feb 6, 2025

achmelo added 3 commits June 17, 2025 10:51
…-indiv-resp

# Conflicts:
#	integration-tests/src/test/java/org/zowe/apiml/functional/gateway/GatewayRoutingTest.java
Copy link

@achmelo achmelo marked this pull request as ready for review June 17, 2025 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants