Skip to content
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.

Sign up for GitHub

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

Update language in test-proxy readme #6057

Merged
merged 18 commits into from
Apr 27, 2023
Merged

Update language in test-proxy readme #6057

Changes from all commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
03a3d7d
ensure conditions all work properly in the case of a previous error
scbedd Jun 2, 2022
cd1cbeb
Merge remote-tracking branch 'upstream/main' into main
scbedd Jun 3, 2022
77a6c4c
Merge branch 'main' of https://github.com/scbedd/azure-sdk-tools into…
scbedd Aug 11, 2022
b32e846
Merge remote-tracking branch 'upstream/main' into main
scbedd Oct 20, 2022
ec5055f
Merge branch 'main' of https://github.com/scbedd/azure-sdk-tools into…
scbedd Nov 15, 2022
b821dc3
Merge remote-tracking branch 'upstream/main' into main
scbedd Nov 15, 2022
9d8e016
Merge remote-tracking branch 'upstream/main' into main
scbedd Jan 4, 2023
b542bd3
Merge branch 'main' of https://github.com/scbedd/azure-sdk-tools into…
scbedd Jan 27, 2023
64071cf
Merge remote-tracking branch 'upstream/main' into main
scbedd Jan 27, 2023
409c72b
Merge remote-tracking branch 'upstream/main'
scbedd Jan 30, 2023
16b8c2b
Merge remote-tracking branch 'upstream/main'
scbedd Jan 31, 2023
a9fd946
Merge remote-tracking branch 'upstream/main'
scbedd Feb 1, 2023
7d8fd11
Merge remote-tracking branch 'upstream/main'
scbedd Feb 21, 2023
75e32f3
Merge remote-tracking branch 'upstream/main'
scbedd Mar 28, 2023
b3c9e05
Merge remote-tracking branch 'upstream/main'
scbedd Mar 28, 2023
e8e5c1d
Merge remote-tracking branch 'upstream/main'
scbedd Apr 4, 2023
9347939
Merge remote-tracking branch 'upstream/main'
scbedd Apr 18, 2023
37206e9
update readme to match reality, a follow-up issue is necessary to add…
scbedd Apr 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions tools/test-proxy/Azure.Sdk.Tools.TestProxy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -581,11 +581,9 @@ The test-proxy offers further customization beyond that offered by sanitizers, m

### Redirection Settings

The test-proxy does NOT transparent follow redirects by default. That means that if the initial request sent by the test-proxy results in some `3XX` redirect status, it **will not** follow. It will return that redirect response to the client to allow THEM to handle the redirect.
The test-proxy follows redirects by default. That means that if the initial request sent by the test-proxy results in some `3XX` redirect status, it **will follow the redirect**.

In certain cases, this is not a possibility for the client. Javascript Browser tests are a great example of this. Since both "modes" are supported, the test-proxy exposes this as a setting `HandleRedirects`.

To set this setting, POST to the `/Admin/SetRecordingOptions` route.
In certain cases, a user will want to utilize both behaviors in their tests. For instance, the javascript `browser` tests run with redirect enabled, however for their `node` versions, the redirect functionality is explicitly disabled. The test-proxy exposes this as a setting `HandleRedirects` within the settings object POST-ed to `/Admin/SetRecordingOptions`.

Example:

Expand Down