From d597aeb508bba77d9961f62ff8fa4c0f93b2784e Mon Sep 17 00:00:00 2001
From: Luc Charland <lcharland@inverse.ca>
Date: Wed, 10 Oct 2012 12:38:23 -0400
Subject: [PATCH] Used POST for the batch delete call instead of parameters

This might have bust the 1024 limit. With post, no problem.
---
 UI/WebServerResources/ContactsUI.js | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/UI/WebServerResources/ContactsUI.js b/UI/WebServerResources/ContactsUI.js
index 35cb33568..ea192bc3f 100644
--- a/UI/WebServerResources/ContactsUI.js
+++ b/UI/WebServerResources/ContactsUI.js
@@ -492,12 +492,13 @@ function onToolbarDeleteSelectedContactsConfirm(dialogId) {
     disposeDialog();
     var contactsList = $('contactsList');
     var rowIds = contactsList.getSelectedRowsId();
-    var urlstr = (URLForFolderID(Contact.currentAddressBook) 
-                 + "/batchDelete?ids=" + rowIds.join("/"));
+    var urlstr = (URLForFolderID(Contact.currentAddressBook) + "/batchDelete");
     for (var i = 0; i < rowIds.length; i++) {
         delete cachedContacts[Contact.currentAddressBook + "/" + rowIds[i]];
     }
-    triggerAjaxRequest(urlstr, onContactDeleteEventCallback, rowIds);
+    triggerAjaxRequest(urlstr, onContactDeleteEventCallback, rowIds,
+                           ('ids=' + rowIds.join("/")),
+                           { "Content-type": "application/x-www-form-urlencoded" });
 }
 
 function onContactDeleteEventCallback(http) {