To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=soap12
HTTP + SOAP12
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /soap12 HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<BlackbooksForRacecardRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions" />
</soap12:Body>
</soap12:Envelope>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<BlackbooksForRacecardResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
<Items xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
<d2p1:BlackbookOnRacecard>
<d2p1:_x003C_BlackbookHighlightID_x003E_k__BackingField>0</d2p1:_x003C_BlackbookHighlightID_x003E_k__BackingField>
<d2p1:_x003C_BlackbookID_x003E_k__BackingField>0</d2p1:_x003C_BlackbookID_x003E_k__BackingField>
<d2p1:_x003C_BlackbookType_x003E_k__BackingField>0</d2p1:_x003C_BlackbookType_x003E_k__BackingField>
<d2p1:_x003C_EventID_x003E_k__BackingField>0</d2p1:_x003C_EventID_x003E_k__BackingField>
<d2p1:_x003C_OutcomeID_x003E_k__BackingField>0</d2p1:_x003C_OutcomeID_x003E_k__BackingField>
</d2p1:BlackbookOnRacecard>
</Items>
</BlackbooksForRacecardResponse>
</soap12:Body>
</soap12:Envelope>