box / box/box-windows-sdk-v2

Setting a new WebProxy still uses the old proxy

Open
#583 6 comments 0 reactions 0 assignees View on GitHub
bug dontstale
Dominant language
C#
Stars
183
Forks
160
Avg merge
10h 44m
Merged PRs (30d)
15

Description

- [x ] I have checked that the [SDK documentation][sdk-docs] and [API documentation][api-docs] doesn't solve my issue

### Description of the Issue
Once you set a WebProxy and attempt authentication, setting a new proxy does not take effect. The code seems to still be using the old proxy.

Setting Proxy Address: proxyabc
Error: One or more errors occurred. An error occurred while sending the request. The remote name could not be resolved: 'proxyabc'.
Setting Proxy Address: proxyxyz
Error: One or more errors occurred. An error occurred while sending the request. The remote name could not be resolved: 'proxyabc'.

### Versions Used
.NET 4.51:

### Steps to Reproduce

### Error Message, Including Stack Trace

[sdk-docs]: ./README.md
[api-docs]: https://developer.box.com/docs

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue through the WebProxy setting and authentication request path described in the report. Verify that changing from proxyabc to proxyxyz causes the subsequent request to use the new proxy; done means the old proxy is no longer used after the WebProxy is replaced.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.