CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail »
  • Using CiviSMTP (Moderator: shane) »
  • Testing the SOAP endpoint to debug "the proxy URL you gave is invalid"
Pages: [1]

Author Topic: Testing the SOAP endpoint to debug "the proxy URL you gave is invalid"  (Read 1760 times)

torenware

  • I post frequently
  • ***
  • Posts: 153
  • Karma: 4
Testing the SOAP endpoint to debug "the proxy URL you gave is invalid"
October 09, 2012, 06:37:29 pm
I'm trying to debug a case where CiviSMTP's config screen gives the cryptic error:

Quote
it appears that the proxy URL you gave is invalid

While this is nice to know, it would be more useful if the error gave some idea as to why that is, so we could actually fix the problem :-)

I'm more than happy to run a bit of SoapClient code so I can debug the server.  But without more info, I'm blind, and can't be of much help.

There's something very old up on the wiki to show an example of what I mean, at http://wiki.civicrm.org/confluence/display/CRM/SOAP+Access+to+CiviCRM+API:

Code: [Select]
<?
$client =& new SoapClient(null, array(
           'location' => 'http://localhost/drupal/modules/civicrm/extern/soap.php',
           'uri' => 'http://localhost')
        );
 
$key = $client->authenticate( DRUPAL_USER_NAME, DRUPAL_USER_PASSWORD );
$params = array('contact_id' => 101);
$returnProperties = null;
$result =& $client->get_contact( $key, $params, $returnProperties );
 
print_r($result);
?>

Ideally, I'd want to know what to use for location/uri, and what to call in order to get the CiviMail processing code to say if it's responsive or not.

At this point, I can tell that my CiviMail endpoint at soap.php responds over HTTP (the logs indicate the endpoint is found, and the server returns 200 OK), but I don't have a clue what else CiviSMTP's automation expects to see but does not see.  Anything that will make that more obvious would be a time saver for everybody involved.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail »
  • Using CiviSMTP (Moderator: shane) »
  • Testing the SOAP endpoint to debug "the proxy URL you gave is invalid"

This forum was archived on 2017-11-26.