HttpWebRequest.ProtocolVersion - how do I set it to try 1.0, then 1.1 (or vice versa)?

Question

HttpWebRequest.ProtocolVersion - how do I set it to try 1.0, then 1.1 (or vice versa)?

David Thielen 3,231

We have a commercial library and some of our customers need

HttpWebRequest.ProtocolVersion=HttpVersion.Version10

and some need

HttpWebRequest.ProtocolVersion=HttpVersion.Version10

Is there a way to tell it to try both? Or do I need to add a configuration setting for the 1.0 people (yuck)?

Also asked on StackOverflow

Xingyu Zhao-MSFT 5,381 Reputation points

2020-12-07T09:18:09.25+00:00

Hi anonymous user ,
Can you find out which users need HTTP 1.0 and set 'HttpWebRequest.ProtocolVersion=HttpVersion.Version10'?
David Thielen 3,231 Reputation points

2020-12-07T13:23:03.803+00:00
Hi XingyuZhao;

Unfortunately no. That would be like telling the VisualStudio team to ask all users of VisualStudio and then set it for each user.

dave

1 answer

Your answer

Xingyu Zhao-MSFT 5,381 Reputation points

2020-12-07T09:18:09.25+00:00

Hi anonymous user ,
Can you find out which users need HTTP 1.0 and set 'HttpWebRequest.ProtocolVersion=HttpVersion.Version10'?
David Thielen 3,231 Reputation points

2020-12-07T13:23:03.803+00:00

Hi XingyuZhao;

Unfortunately no. That would be like telling the VisualStudio team to ask all users of VisualStudio and then set it for each user.

dave

Answer 1

cheong00 3,491 Volunteer Moderator

I think the most feasible solution would be to deploy Nginx as forward proxy with your program to visit those URL with "proxy_http_version 1.0", then point the defaultProxy setting of your application to it.

David Thielen 3,231 Reputation points

2020-12-08T10:36:37.17+00:00

Hi cheong00;

That would be overkill. Asking 40,000 business users to install Nginx to provide a solution for one customer doesn't make sense.

thanks - dave
cheong00 3,491 Reputation points Volunteer Moderator

2020-12-08T10:41:45.417+00:00

Last time I checked the expanded Nginx package is only around 4 MB, which is much smaller than lots of commercial framework libraries, perfectly reasonable to include it in solution to "just serve your application". (Hence the need to change "defaultProxy" settings instead of rely on automatic proxy detection)

And a workaround is only an overkill if there exists other way to workaround the problem.

Share via

HttpWebRequest.ProtocolVersion - how do I set it to try 1.0, then 1.1 (or vice versa)?

1 answer

Your answer