Document the default request timeout and HTTP without a redirect - #130
Merged
csandanov merged 1 commit intoSep 28, 2026
Conversation
App environments use a request timeout of 0s, so requests have no total time limit, and a finite timeout also cuts off long downloads and streamed responses. With the HTTPS redirect turned off, a domain with a TLS certificate serves the app over both HTTP and HTTPS.
csandanov
added this pull request to stack #131
September 28, 2026 08:07
csandanov
marked this pull request as ready for review
September 28, 2026 08:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two route settings behave differently in the next release, and the route settings page should say so:
request_timeoutof0sby default, so requests have no total time limit. Previously a route without a timeout used the gateway's own default. A finite request timeout also covers sending the whole response, so it cuts off downloads and streamed responses that take longer.404.Changes
trueandfalsedo.0sdefault, when existing app environments switch to it, and why a finite timeout also limits downloads and streams.0srequest timeout.This PR is stacked on #129, which removes the retired default rate limits from the same list. It stays a draft until both behaviors are released.
Validation