Re: The underlying connection was closed

"kirk" <nokirkspam@xxxxxxxxxxxxxxxxx> wrote in message
news:OtgzjzRgHHA.4704@xxxxxxxxxxxxxxxxxxxxxxx
John,

1) The solutions I was finding on the web were all based on the 1.1 and
1.0 framework. They involved tweaking the resource.cs file by overriding
the WebRequest method and setting the KeepAlive = false. Basicly, force
the creation of a new connection for every request. I guess that MS had a
support item on it at
'http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b819450' but
they have since removed the topic.
I can't follow the recommend because in VS 2005, there is no resource.cs
file any more. this file is generated on the fly by the .net framework
after deployment.

2) the web service is configured for ssl using a purchased certificate.
When my client hits my ws using https, my call to the 3rd party ws fails
with the error stated. If I allow my client to hit my ws without ssl, my
call to the 3rd party ws works just fine. In both cases I am hitting the
3rd party ws using ssl.

Your call to the 3rd party ws should be independent of how your ws was
called. The information that you were called over an SSL connection simply
should not be able to flow to the call on the 3rd party ws.

Unless, that is, you're doing something to couple the two. For instance, are
you using properties of the Request to set parameters for the call to the
3rd party ws? Look for any way that the information could be leaking from
the call to your client into the call to the other ws.
--
John Saunders [MVP]


.

Relevant Pages

  • Re: The underlying connection was closed
    ... this file is generated on the fly by the .net framework ... the web service is configured for ssl using a purchased certificate. ... When my client hits my ws using https, my call to the 3rd party ws fails ... I have written a web service that calls another web service. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: The underlying connection was closed
    ... It turns out that I had a custom component I had written named security.dll ... the web service is configured for ssl using a purchased certificate. ... When my client hits my ws using https, my call to the 3rd party ws fails ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: MVPs and Terminal Services
    ... The need for third party software is indeed annoying (and a real financial ... the client of the actual features and limitations so the client isn't ... I'm a former MVP myself, and still answer questions in forums where I ... responses I'd have sent him mail, ...
    (microsoft.public.windows.terminal_services)
  • Re: Using CAPI to encrypt in AES CBC mode without padding
    ... Faris's framework. ... Get your indirectly exploding clarity behind my ... party. ... it concerns a rush too successful away from her ...
    (sci.crypt)
  • ADAM & SSL (w/ 3rd Party)
    ... Has anyone been able to get ADAM working with SSL using a certificates ... issued from a 3rd party CA such as Verisign? ... Verisign tells us the created .CSR file does not contain required ... LDAP over SSL? ...
    (microsoft.public.windows.server.active_directory)
Loading