title: not sure if this is my mistake ~~ vs2010 Add Service Reference fails
body: <p><a href="https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter" rel="nofollow">https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter</a>  </p>
  
  <p>the above is from Taleo's API guide.<br>
  I'm trying to create a WCF Client<br>
  (e.g.:  " Creating Your First WCF Client"<br>
     <a href="http://channel9.msdn.com/shows/Endpoint/Endpoint-Screencasts-Creating-Your-First-WCF-Client/" rel="nofollow">http://channel9.msdn.com/shows/Endpoint/Endpoint-Screencasts-Creating-Your-First-WCF-Client/</a>  )  </p>
  
  <p>The tbe.taleo... link is from Taleo's API documentation.  </p>
  
  <p>Likely my understanding is flawed.  My assumption is that when the<br>
  link from Taleo is entered into the vs2010 "Add Service Reference"<br>
  dialog and <strong>GO</strong> is clicked, then vs2010 should retrieve<br>
  a proper WSDL/SOAP envelope back from the Taleo link.<br>
  That <strong><em>does not</em></strong> happen; instead an error occurs.<br>
  Fiddler2 (http://fiddler2.com) displays the status code 500<br>
  "HTTP/1.1 500 Internal Server Error".  [FULL DETAILS BELOW]  </p>
  
  <p>"<strong>WcfTestClient.exe</strong>" gives a similar error:  [WcfTestClient DETAILS BELOW]  </p>
  
  <p><strong>QUESTION:</strong>  is it me, or is the Taleo link flawed?  </p>
  
  <p>Thank you,<br>
  Gerry  </p>
  
  <p><strong>[FULL DETAILS "Add Service Reference"]</strong><br>
  The HTML document does not contain Web service discovery information.
  Metadata contains a reference that cannot be resolved: 'https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter'.
  The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 544 bytes of the response were: '
  
  
  
  SOAP-ENV:Protocol
  Unsupported content type &quot;application/soap+xml; charset=utf-8&quot;, must be: &quot;text/xml&quot;.
  /MANAGER/dispatcher/servlet/rpcrouter
  </p>
  
  <p>
  
  '.
  The remote server returned an error: (500) Internal Server Error.
  If the service is defined in the current solution, try building the solution and adding the service reference again.  </p>
  
  <p><strong>[WcfTestClient DETAILS]</strong><br>
  Error: Cannot obtain Metadata from <a href="https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter" rel="nofollow">https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter</a> If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address.  For help enabling metadata publishing, please refer to the MSDN documentation at <a href="http://go.microsoft.com/fwlink/?LinkId=65455.WS-Metadata" rel="nofollow">http://go.microsoft.com/fwlink/?LinkId=65455.WS-Metadata</a> Exchange Error    URI: <a href="https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter" rel="nofollow">https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter</a>    Metadata contains a reference that cannot be resolved: 'https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter'.    The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 544 bytes of the response were: 'SOAP-ENV:ProtocolUnsupported content type &quot;application/soap+xml; charset=utf-8&quot;, must be: &quot;text/xml&quot;./MANAGER/dispatcher/servlet/rpcrouter'.    The remote server returned an error: (500) Internal Server Error.HTTP GET Error    URI: <a href="https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter" rel="nofollow">https://tbe.taleo.net/MANAGER/dispatcher/servlet/rpcrouter</a>    The HTML document does not contain Web service discovery information.</p>