I have an asp.net website that my clients use via SSL. I need another http
communication within a postback to receive remote data to fulfill my current
postback request operation. I have to listen to this ssl/http request on
port 443 but a different uri prefix. If I use HttpListener, can I then use
SslStream on the Request.InputStream to receive and decrypt data? I saw
examples on the net where a different port was used and configured using
httpcfg.exe tool but my constraint binds me only to 443 and since IIS owns
that port I cannot use this tool.
Build an ASP.Net HttpHandler for that URI that handles the request, and pass
the information received to whatever you want to.

Signature
HTH,
Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP
>I have an asp.net website that my clients use via SSL. I need another http
>communication within a postback to receive remote data to fulfill my
[quoted text clipped - 4 lines]
>configured using httpcfg.exe tool but my constraint binds me only to 443
>and since IIS owns that port I cannot use this tool.
Ashish Kaila - 13 Dec 2007 13:11 GMT
But how do I retrieve the information in the waiting postback session?
HttpHandler and postback are two different sessions. And I may have several
of the postback sessions. The way I was thinking of differentiating was to
choose a unique uri prefix every time.
> Build an ASP.Net HttpHandler for that URI that handles the request, and
> pass the information received to whatever you want to.
[quoted text clipped - 7 lines]
>>configured using httpcfg.exe tool but my constraint binds me only to 443
>>and since IIS owns that port I cannot use this tool.
Kevin Spencer - 14 Dec 2007 13:01 GMT
You create an HttpRequest to the HttpHandler.

Signature
HTH,
Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP
> But how do I retrieve the information in the waiting postback session?
> HttpHandler and postback are two different sessions. And I may have
[quoted text clipped - 12 lines]
>>>and configured using httpcfg.exe tool but my constraint binds me only to
>>>443 and since IIS owns that port I cannot use this tool.