Certificates and WebRequest

[Bobstar]

Hello..

In the good old days where I programmed using wininet.dll, I did'nt need to do anything to retrieve a sourcecode from a secureed site eg. HTTPS - port 443.

But in the new .NET it seems a lot more difficult, infact I dont seem to be able to solve a webrequest using SSL.

How do I manage a certificat in .NET

I cant understand why it's not built in just like the new cookiecontainer etc

Regard

[Nicholas Paldino [.NET/C# MVP]]

Bobstar,

It is. Have you checked out the ClientCertificates property on the
HttpWebRequest class? It should give you the functionality you need to
manage your own certificates (if you need to).

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Bobstar" <an*******@discussions.microsoft.com> wrote in message
news:0D**********************************@microsof t.com...

Hello...

In the good old days where I programmed using wininet.dll, I did'nt need to do anything to retrieve a sourcecode from a secureed site eg. HTTPS -
port 443.
But in the new .NET it seems a lot more difficult, infact I dont seem to be able to solve a webrequest using SSL.
How do I manage a certificat in .NET?

I cant understand why it's not built in just like the new cookiecontainer etc.
Regards

[Nicholas Paldino [.NET/C# MVP]]

Bobstar,

It is. Have you checked out the ClientCertificates property on the
HttpWebRequest class? It should give you the functionality you need to
manage your own certificates (if you need to).

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Bobstar" <an*******@discussions.microsoft.com> wrote in message
news:0D**********************************@microsof t.com...

Hello...

In the good old days where I programmed using wininet.dll, I did'nt need to do anything to retrieve a sourcecode from a secureed site eg. HTTPS -
port 443.
But in the new .NET it seems a lot more difficult, infact I dont seem to be able to solve a webrequest using SSL.
How do I manage a certificat in .NET?

I cant understand why it's not built in just like the new cookiecontainer etc.
Regards

[Nicholas Paldino [.NET/C# MVP]]

Bobstar,

If the protocol is HTTPS, then the port number is assumed to be 443 by
default (just like it is assumed to be port 80 by default for HTTP). If you
are using the standard assigned ports, then you don't need to specify them.
If you are not, then you must specify them.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Bobstar" <an*******@discussions.microsoft.com> wrote in message
news:77**********************************@microsof t.com...

Thank you...
Just wondering (that's the way it's in wininet.dll), could the trouble be caused by a wrong port number ?. Is it being set automatically in
WebRequest? - Or do I have to specify port 80/ 443 ??
Kind regards

[Nicholas Paldino [.NET/C# MVP]]

Bobstar,

If the protocol is HTTPS, then the port number is assumed to be 443 by
default (just like it is assumed to be port 80 by default for HTTP). If you
are using the standard assigned ports, then you don't need to specify them.
If you are not, then you must specify them.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Bobstar" <an*******@discussions.microsoft.com> wrote in message
news:77**********************************@microsof t.com...

Thank you...
Just wondering (that's the way it's in wininet.dll), could the trouble be caused by a wrong port number ?. Is it being set automatically in
WebRequest? - Or do I have to specify port 80/ 443 ??
Kind regards