[arin-tech-discuss] arin-tech-discuss Digest, Vol 7, Issue 3
Grimes, Ronald
Ron.Grimes at qwest.com
Thu Jun 9 16:28:29 EDT 2011
Hi Tim,
Could you please look at the below. We do not seem to be receiving the "Codes" for errors below? Could you help us out with this concern?
Thanks,
Ron
-----Original Message-----
From: Zhao, Sean
Sent: Thursday, June 09, 2011 4:24 PM
To: Grimes, Ronald
Subject: RE: arin-tech-discuss Digest, Vol 7, Issue 3
Ron, I sent an xml with an empty <orgHandle>
I got an exception instead of error message. Here is the xml I sent
<?xml version="1.0" encoding="UTF-8"?>
<net xmlns="http://www.arin.net/regrws/core/v1">
<version>4</version>
<orgHandle></orgHandle>
<parentNetHandle>NET-208-44-0-0-1</parentNetHandle>
<netName>Q0609-208-44-99-48</netName>
<netBlocks>
<netBlock xmlns="">
<type>S</type>
<startAddress>208.44.99.48</startAddress>
<cidrLength>29</cidrLength>
</netBlock>
</netBlocks>
<originASes>
<originAS xmlns="">209</originAS>
</originASes>
</net>
But instead of getting an xml error message, I got this, "Server returned HTTP response code: 400 for URL: https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey"
Second time I sent an xml with orgHandle,
<?xml version="1.0" encoding="UTF-8"?>
<net xmlns="http://www.arin.net/regrws/core/v1">
<version>4</version>
<orgHandle>BNO</orgHandle>
<parentNetHandle>NET-63-144-0-0-1</parentNetHandle>
<netName>Q0609-63-146-48-0</netName>
<netBlocks>
<netBlock xmlns="">
<type>S</type>
<startAddress>63.146.48.0</startAddress>
<cidrLength>29</cidrLength>
</netBlock>
</netBlocks>
<originASes>
<originAS xmlns="">209</originAS>
</originASes>
</net>
I got a good an xml returned, like following,
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ticketedRequest xmlns="http://www.arin.net/regrws/core/v1">
<net>
<pocLinks/>
<netBlocks>
<netBlock>
<cidrLength>29</cidrLength>
<description>Reassigned</description>
<endAddress>063.146.048.007</endAddress>
<startAddress>063.146.048.000</startAddress>
<type>S</type>
</netBlock>
</netBlocks>
<handle>NET-63-146-48-0-1</handle>
<netName>Q0609-63-146-48-0</netName>
<orgHandle>BNO</orgHandle>
<originASes>
<originAS>AS209</originAS>
</originASes>
<parentNetHandle>NET-63-144-0-0-1</parentNetHandle>
<registrationDate>2011-06-09T16:11:13.059-04:00</registrationDate>
<version>4</version>
</net>
</ticketedRequest>
Thanks,
Sean Zhao
Sean.Zhao at CenturyLink.com
-----Original Message-----
From: arin-tech-discuss-bounces at arin.net [mailto:arin-tech-discuss-bounces at arin.net] On Behalf Of arin-tech-discuss-request at arin.net
Sent: Thursday, June 09, 2011 12:00 PM
To: arin-tech-discuss at arin.net
Subject: arin-tech-discuss Digest, Vol 7, Issue 3
Send arin-tech-discuss mailing list submissions to
arin-tech-discuss at arin.net
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.arin.net/mailman/listinfo/arin-tech-discuss
or, via email, send a message with subject or body 'help' to
arin-tech-discuss-request at arin.net
You can reach the person managing the list at
arin-tech-discuss-owner at arin.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of arin-tech-discuss digest..."
Today's Topics:
1. Re: Restful web service for Swipping (Tim Christensen)
----------------------------------------------------------------------
Message: 1
Date: Thu, 9 Jun 2011 14:04:10 +0000
From: Tim Christensen <timc at arin.net>
To: "Grimes, Ronald" <Ron.Grimes at qwest.com>,
"'arin-tech-discuss at arin.net'" <arin-tech-discuss at arin.net>
Cc: "Zhao, Sean" <Sean.Zhao at qwest.com>
Subject: Re: [arin-tech-discuss] Restful web service for Swipping
Message-ID: <CA164B15.28773%timc at corp.arin.net>
Content-Type: text/plain; charset="us-ascii"
On 6/9/11 8:29 AM, "Grimes, Ronald" <Ron.Grimes at qwest.com> said:
> I went through the document and saw the following on page 22 (in attachment).
> These are some of the details we are looking for. We are not seeing error
> messages like this come back in production. Do you know if this is currently
> working?
Yes. These messages appear in the Error Payload that is returned in the
*body* of the HTTP Response. For example, I tried to perform a GET on a POC
record to which a bogus API key does not have access (e.g., would produce an
authentication failure) by issuing a GET such as:
http://www.arin.net/rest/poc/ARIN-HOSTMASTER?apikey=API-BOGUS
And received an HTTP response of "400 Bad Request", containing the following
Error Payload in the HTTP body:
<error xmlns="http://www.arin.net/regrws/core/v1">
<additionalInfo/>
<code>E_AUTHENTICATION</code>
<components/>
<message>The API key specified was missing or invalid.</message>
</error>
> Do you know if there are any plans to make these error messages more specific?
These messages are intended to provide a categorical indication of the
problem. The reason for the specific error is informed by examining the
specific URI, inbound payload, and comparison to the published XML schemas
that are available in the same location where you found the Methods and
Payloads documents.
> Do you know how long it will be before these documents will be updated to be
> more user friendly?
One focus of the document update is to address this particular issue: how to
contextually correlate an error using the Payload, XML Schema, and other
documentation so that you can understand and resolve errors readily.
Revising the document is an active work item right now, but must also go
thru publishing and approval. In the meantime, you may continue to ask
questions here on ARIN-Tech-Discuss. Please know that your questions and
feedback are very valuable: they indicate to us what areas of the
documentation need to be improved or refined.
Best regards,
Tim Christensen
ARIN Engineering
------------------------------
_______________________________________________
arin-tech-discuss mailing list
arin-tech-discuss at arin.net
http://lists.arin.net/mailman/listinfo/arin-tech-discuss
End of arin-tech-discuss Digest, Vol 7, Issue 3
***********************************************
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
More information about the arin-tech-discuss
mailing list