[proxy] Pre-flight server authentication related endpoints to add additional latency #15078
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.
Description
Pre-flight requests to
server
/auth/*
endpoints in order to decide whether to send the actual request toserver
orslow-server
depending on the value of theslow_database
feature flag.This change will affect requests to following paths on
server
:/auth/github/callback /auth /auth/* /apps /apps/*
The pre-flight approach taken here is the same as we use for other
api/*
endpoints (#14897) and websocket connections (#15035).Related Issue(s)
Part of #9198 and #14965
How to test
slow_database
feature flag for your user id in the preview.Release Notes
Documentation
Werft options:
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh