Hi Michael,

I use PHP so I don't know if this applies but  I include  a Content-Length
header:

Content-Length: [length of the XML]

here's a working XML snippet:

<?xml version='1.0' encoding="UTF-8" standalone="no" ?>
<!DOCTYPE OPS_envelope SYSTEM "ops.dtd">
<OPS_envelope>
<header>
<version>0.9</version>
</header>
<body>
<data_block><dt_assoc>
<item key="protocol">XCP</item>
<item key="action">SET</item>
<item key="object">COOKIE</item>
<item key="registrant_ip">[the IP address]</item>
<item key="attributes"><dt_assoc>
<item key="domain">[domain.com]</item>
<item key="reg_username">[user]</item>
<item key="reg_password">[password]</item>
</dt_assoc>
</item>
</dt_assoc></data_block>
</body>
</OPS_envelope>


Thank you for your suggestion. However, I don't think my problem has anything to do with the XML I send. I get the same error (401) even when I do an API WHOIS, or when I use a wrong private key.

I will try the content length header, though... but if that helpded, that would be strange, as my perl code is basically the same as the one in the examples.

Regards,
- Csongor



Reply via email to