Sending HTTP requests with C# HttpWebRequest or WebClient?

Question

I can use both HttpWebRequest to send an HTTP request and get an HTTP response without a WebClient.

When should you use HttpWebRequest and when should you use WebClient?

Almost the same question as http://stackoverflow.com/questions/4123543/design-question — Tim Robinson, Nov 09 '10 at 13:18

score 3 · Answer 1 · answered Nov 09 '10 at 13:16

3

WebClient can be used when you don't need any fine-tuning.

When using HttpWebRequest, you can control various options, including timeouts (very important). So basically - WebClient for toy projects / POCs, HttpWebRequest for actual business.

answered Nov 09 '10 at 13:16

ripper234

222,824
274
634
905

score 1 · Answer 2 · answered Nov 09 '10 at 13:17

1

Personally I always use WebClient. The API seems more simple. It uses HttpWebRequest under the covers.

answered Nov 09 '10 at 13:17

Darin Dimitrov

1,023,142
271
3,287
2,928

score 0 · Answer 3 · edited May 23 '17 at 11:43

0

WebClient is ideal for downloads and uploads.

HttpWebRequest is ideal for web connections, including sending HTTP POST requests, as seen here: HTTP request with post

edited May 23 '17 at 11:43

Community

1
1

answered Nov 09 '10 at 13:20

Evan Mulawski

54,662
15
117
144

score 0 · Answer 4 · answered Nov 09 '10 at 13:21

0

If you do not need access to the underlying stream but are just uploading or downloading "data", i.e. a file some bytes or a string, WebClient is a simplifying abstraction.

answered Nov 09 '10 at 13:21

BrokenGlass

158,293
28
286
335

Sending HTTP requests with C# HttpWebRequest or WebClient?

4 Answers4