Loading ...
Sorry, an error occurred while loading the content.

7249XMLBus Server Interop issue

Expand Messages
  • Daniel Kulp
    Mar 1, 2002
      Hi all,

      During the interop event this week, a couple of the vendors reported an
      issue with the XMLBus server returning WSDL where the SOAP location URL
      did not contain the port number. I've been trying to do some research on
      this issue and it looks to me like it is a bug in the clients that are
      downloading the WSDL, not the XMLBus server.

      Basically, the XMLBus server uses the "Host" HTTP header (if available)
      to create the URL that is used in the WSDL. This allows the server to be
      bound to multiple ports and whatever port the client was talking to is
      what will be represented in the WSDL. However, some of the SOAP clients
      are setting that header to just
      Host: interop.xmlbus.com
      Host: interop.xmlbus.com:7002

      I took a look at the HTTP 1.1 protocol specification (rfc 2616)
      (http://www.ietf.org/rfc/rfc2616.txt) and according to section
      14.23, the Host header MUST contain the port number if it isn't the
      default port (80 for http).

      Anyway, I wanted to post this to SOAP Builders as this really is an
      interop issue. I wanted to let everyone know about it so the bugs in the
      client HTTP stacks can be worked out as well as the bugs in the SOAP


      J. Daniel Kulp
      Principal Engineer
      P: 781-902-8727 C: 617-513-4582 F:781-902-8001
    • Show all 2 messages in this topic