"Ashish, FL" <Ashish, FL@discussions.microsoft.com> wrote in message
news:427EDF59-E25D-49F6-AC27-ABEF798D9AD1@microsoft.com...
> Hi all:
>
> My old application used to POST xml to a remote server using
HttpWebRequest
> from within an aspx page. The process worked like a charm (though
sometimes I
> experienced delays in receiving a response). Using the .NET class similar
to
> http://support.microsoft.com/kb/330589/EN-US/#7
>
> Now, I am required to make that POST xml request over HTTPS instead of
HTTP.
> I have no ideas what to do, where to begin. Ofcourse, just changing the
> posturl from "http://" to "https://" didn't work (as expected, hehehe).
Can
> anyone throw some pointers...?
>

"Ken Dopierala Jr." wrote:

> Hi,
>
> You probably need to define a custom security policy. A browser has this
> built in but HttpWebRequest doesn't. You'll want to search for
> System.Net.ICertificatePolicy to find out how to create these. Good luck!
> Ken.
>
> --
> Ken Dopierala Jr.
> For great ASP.Net web hosting try:
> http://www.webhost4life.com/default.asp?refid=Spinlight
> If you sign up under me and need help, email me.
>
> "Ashish, FL" <Ashish, FL@discussions.microsoft.com> wrote in message
> news:427EDF59-E25D-49F6-AC27-ABEF798D9AD1@microsoft.com...
> > Hi all:
> >
> > My old application used to POST xml to a remote server using
> HttpWebRequest
> > from within an aspx page. The process worked like a charm (though
> sometimes I
> > experienced delays in receiving a response). Using the .NET class similar
> to
> > http://support.microsoft.com/kb/330589/EN-US/#7
> >
> > Now, I am required to make that POST xml request over HTTPS instead of
> HTTP.
> > I have no ideas what to do, where to begin. Ofcourse, just changing the
> > posturl from "http://" to "https://" didn't work (as expected, hehehe).
> Can
> > anyone throw some pointers...?
> >
>
>