- Contents
SOAP API Developer's Guide
Response (Transport Control)
The following schema describes the transport control data for the HTTP transport. The HTTP element is the child element of the TransportCtrl element.
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="HTTP" type="HTTP"/>
<xsd:complexType name="HTTP">
<xsd:sequence>
<xsd:element name="Headers" type="Headers" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="statusCode" type="xsd:positiveInteger" use="optional"/>
<xsd:attribute name="statusText" type="xsd:string" use="optional"/>
</xsd:complexType>
<xsd:complexType name="Headers">
<xsd:element name="Header" type="Header" minOccurs="0" maxOccurs="unbounded"/>
</xsd:complexType>
<xsd:complexType name="Header">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="name" type="xsd:string" use="required"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>
Response Transport Example
The following is an example of a transport control response structure that "asks" the ISAPI listener to send a 501 error (Not Implemented) back to the client. The default status codes are 200 (OK) for successfully processed requests, and 500 (Internal Server Error) for failed requests (body contains a <Fault> element).
<TransportCtrl>
<HTTP statusCode="501" statusText="Not Implemented"/>
</TransportCtrl>
Tip—Header fields specified in the TransportControl structure will have precedence over the default headers generated by the ISAPI listener (such as "Content-Type:text/xml").