The Fiddler FAQ gives the answer to this. You essentially route your HTTP traffic through Fiddler (i.e. Use Fiddler as a proxy). Here’s some links that will help: Fiddler Web Debugging – Configuring Clients Which in turn links to here: Take the Burden Off Users with Automatic Configuration in .NET You can achieve this via … Read more
Using a try/catch block like this and processing the error message appropriately should work fine: var request = (HttpWebRequest)WebRequest.Create(address); try { using (var response = request.GetResponse() as HttpWebResponse) { if (request.HaveResponse && response != null) { using (var reader = new StreamReader(response.GetResponseStream())) { string result = reader.ReadToEnd(); } } } } catch (WebException wex) { … Read more
Use this code to disable HTTP Keep-Alive on the client: _http.DefaultRequestHeaders.ConnectionClose = true; This will set Connection request header to close.
I found the answer, It was because the third party webservice we were calling did not support TLS 1.0 they supported 1.1 and 1.2. So I had to change the security protocol. ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;
An enum doesn’t make much sense. MIME types are open-ended. That is, the list is not finite: new types are added from time to time. See RFC4288: Media Type Specifications and Registration Procedures
You can use StreamReader.ReadToEnd(), using (Stream stream = response.GetResponseStream()) { StreamReader reader = new StreamReader(stream, Encoding.UTF8); String responseString = reader.ReadToEnd(); }
Is this possible using HttpWebRequest and HttpWebResponse? You could have your web server simply catch and write the exception text into the body of the response, then set status code to 500. Now the client would throw an exception when it encounters a 500 error but you could read the response stream and fetch the … Read more
Note that RFC 6266 supersedes the RFCs referenced below. Section 7 outlines some of the related security concerns. The authority on the content-disposition header is RFC 1806 and RFC 2183. People have also devised content-disposition hacking. It is important to note that the content-disposition header is not part of the HTTP 1.1 standard. The HTTP … Read more
Using HttpWebRequest gives you more control on the request. You can set cookies, headers, protocol, etc… In the response, you can also retrieve the cookies and headers
The correct way could be: Content-Disposition: inline; filename=”myfile.txt”