[openstack-dev] [neutron][api] GET call with huge argument list

Doug Wiegley dougwig at parksidesoftware.com
Wed Jan 20 00:14:13 UTC 2016


It would have to be a POST, but even that will start to have timeout issues. An API which requires that kind of input is kind of a bad idea. Perhaps you could describe what you’re trying to do?

Thanks,
doug

> On Jan 19, 2016, at 4:59 PM, Shraddha Pandhe <spandhe.openstack at gmail.com> wrote:
> 
> Hi folks,
> 
> 
> I am writing a Neutron extension which needs to take 1000s of network-ids as argument for filtering. The CURL call is as follows:
> 
> curl -i -X GET 'http://hostname:port/neutron/v2.0/extension_name.json?net-id=fffecbd1-0f6d-4f02-aee7-ca62094830f5&net-id=fffeee07-4f94-4cff-bf8e-a2aa7be59e2e' -H "User-Agent: python-neutronclient" -H "Accept: application/json" -H "X-Auth-Token: cccccccccccccccccccccccccccccccc"
> 
> 
> The list of net-ids can go up to 1000s. The problem is, with such large url, I get the "Request URI too long" error. I don't want to update this limit as proxies can have their own limits.
> 
> What options do I have to send 1000s of network IDs? 
> 
> 1. -d '{}' is not a recommended option for GET call and wsgi Controller drops the data part when routing the request.
> 
> 2. Use POST instead of GET? I will need to write the get_<resource> logic inside create_resource logic for this to work. Its a hack, but complies with HTTP standard.
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160119/3b2bc624/attachment.html>


More information about the OpenStack-dev mailing list