[db-wg] API - INET6NUM Object Creation Bug

Denis,

I appreciate the response and indication of this. So that I am able to 
effectively communicate this to the rest of my team though, is there an 
ETA on this release?

Thanks!

Tim Garrison
Software Engineer II
tgarrison at softlayer.com
281.714.4213 Direct
713.540.4325 Cell
866.398.7638 Toll-Free
281.714.4657 Fax

SoftLayer Technologies, Inc.
315 Capitol Street
Suite 205
Houston, TX 77002
http://www.softlayer.com/

On 06/10/2013 10:50 AM, Denis Walker wrote:
> Dear Tim Garrison,
>
> The RIPE NCC has been working on a new version of the API interface. 
> This will be almost 100% backwards compatible except for a few cases 
> where the old API was not complete or had shortcomings. This problem 
> you are experiencing will be fixed by this new release. We expect to 
> deploy this very soon. It will be announced on this mailing list when 
> the deployment is made.
>
> Regards
> Denis Walker
> Business Analyst
> RIPE NCC Database Group
>
> On 07/06/2013 21:05, Tim Garrison wrote:
>> Greetings,
>>
>> I have understood that doing an HTTP POST to
>> https://apps.db.ripe.net/whois/create will respond with an HTTP201
>> status code and a 'Location' header pointing to the created object.
>>
>> This seems to work great for 'inetnum' and 'person' objects, but I've
>> discovered that for 'inet6num' objects, the parent network block's
>> handle is used in this header.
>>
>> This is creating problems for me in my current project, and I was
>> wondering if someone could possibly take a look.
>>
>> Thanks!
>>
>