[go: nahoru, domu]
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

Jump to bottom

Set-AzureRmApplicationGatewayBackendHttpSettings resets Request Timeout to 30 seconds when RequestTimeout parameter is not set #5145

Open
ukienet opened this issue Dec 14, 2017 · 3 comments
Open

Set-AzureRmApplicationGatewayBackendHttpSettings resets Request Timeout to 30 seconds when RequestTimeout parameter is not set #5145

ukienet opened this issue Dec 14, 2017 · 3 comments
Assignees
@akshaysngupta
Labels
customer-reported Network - Application Gateway Network Service Attention This issue is responsible by Azure service team.

Comments

@ukienet
Copy link
ukienet commented Dec 14, 2017 •
edited by azuresdkci
Loading

Cmdlet(s)

Set-AzureRmApplicationGatewayBackendHttpSettings

PowerShell Version

Instructions: to get PowerShell version, type $PSVersionTable and look for the value associated with PSVersion

5.1.14393.1770

Module Version

OS Version

Instructions: to get OS version, type $PSversionTable and look for value associated with BuildVersion

10.0.14393.1770

Description

Set-AzureRmApplicationGatewayBackendHttpSettings overrides Request Timeout to 30 seconds when RequestTimeout parameter is not specified.

I have an existing backend http settings with 120 seconds timeout. I then call Set-AzureRmApplicationGatewayBackendHttpSettings to change the port of that setting, without passing the RequestTimeout parameter.

According to documentation the RequestTimeout parameter is optional and has no default value.

Howerver in my case the call to Set-AzureRmApplicationGatewayBackendHttpSettings resets the request timeout back to 30 seconds.

My workaround for now is to specify the optional RequestTimeout parameter.

Debug Output

Instructions: to get Debug Output, set $DebugPreference="Continue" and then execute the cmdlet or script causing the issue

Script/Steps for Reproduction
@maddieclayton
Copy link
Contributor

@DeepakRajendranMsft Can you take a look?

@maddieclayton
Copy link
Contributor

@akshaysngupta Can you take a look at this issue?

@akshaysngupta
Copy link
Member

Taking a look.

@bsiegel bsiegel added the Service Attention This issue is responsible by Azure service team. label Sep 26, 2018
@EvgenyAgafonchikov EvgenyAgafonchikov mentioned this issue Jan 24, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akshaysngupta akshaysngupta

Labels
customer-reported Network - Application Gateway Network Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@bsiegel @akshaysngupta @DeepakRajendranMsft @maddieclayton @ukienet @shahabhijeet @chandrasekarsrinivasan @azure-sdk