Trying to impersonate a browser on Https

Question

0.00/5 (No votes)

See more:

Hello.

I am developing a simple application which tries to simulate the
html anchor.
I verified that, using the anchor in a simple javascript, I can correctly load
the web page using https.
When it comes to simulate that behaviour in my application , I keep getting the
"Remote Server Error 500 (Internal Server Error)".

The application code is the following :

WebRequest WRq = WebRequest.Create(UrlForPost2);

WRq.AuthenticationLevel = System.Net.Security.AuthenticationLevel.MutualAuthRequested; ServicePointManager.ServerCertificateValidationCallback = new System.Net.Security.RemoteCertificateValidationCallback(AcceptAllCertifications);

WRq.Method = "GET";

((HttpWebRequest)WRq).ProtocolVersion = HttpVersion.Version11;

WebResponse WRe = WRq.GetResponse();
Stream S = WRe.GetResponseStream();

The exception is thrown by the WRq.GetResponse () . I wonder if, prior to sending the request, I should request a digital certificate to send with the request......

Thank you in advance

Leo

Posted 25-Aug-14 4:03am

tiwal

Add a Solution

Comments

Sergey Alexandrovich Kryukov 25-Aug-14 12:20pm

Not clear from the very beginning. What does it mean, "simulate the anchor", by means of what? What does it mean, "to impersonate a browser"? (Is a browser a person? :-)
Maybe what you are trying to do is very clever and makes sense, but it's hard to see from your post.
—SA

tiwal 26-Aug-14 5:11am

Well I'll try to be clearer then . I have a web page that, at a certain point , has a

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)