As another poster was hinting, this is a job for HTTP POST, not HTTP GET. GET puts all arguments into the URL. POST puts a short URL, and then adds all of the arguments to the hidden handshaking conversation that follows the network connection. The good news is that many CGI programs don't even notice that you've made the request in a different way. The program just gets its arguments and is happy. The bad news is that this is not guaranteed.
(A side benefit of POST is that all of these ugly or semi- private facts don't show up in the URL.) If you can't accept HTTP POST arguments this way for some reason but you can modify the CGI script (recipeBatch in your example), then you may get a little farther by compacting the arguments a bit. You have a couple hundred copies of the characters '&ids='. Make it one argument with + separators, and split it on the CGI side. That gives you a little bit of room, but it's not unlimited by URL length like POST is. I am hoping that those 7-digit numbers are not phone numbers. I'd hate to think I was helpful AT ALL to someone building an annoying telemarketing system. On Apr 8, 3:18 am, imran ali <[email protected]> wrote: > Hi all, > i have to download data but having big ur,l it's character is going to > increase more than 4048, > for small url it is working fine but for big url it has been giving > response code 414- url too long. > what would be feasible way to handle this issue? > > example of url is > "http://www.someserver.com/api/recipeBatch? > ids=4851525&ids=4853720&ids=4856090&ids=4856180&ids=4856578&ids= ... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
