Add read-only access to POST data for webRequest's onBeforeRequest

chrome/common/extensions/api/web_request.json

Index: chrome/common/extensions/api/web_request.json
diff --git a/chrome/common/extensions/api/web_request.json b/chrome/common/extensions/api/web_request.json
index af94afe869f5b54bae7412ffbe85889105e7099c..886af8f8faea52f41c5c6abefae813825e3f125b 100644
--- a/chrome/common/extensions/api/web_request.json
+++ b/chrome/common/extensions/api/web_request.json
@@ -106,6 +106,23 @@
               "method": {"type": "string", "description": "Standard HTTP method."},
               "frameId": {"type": "integer", "description": "The value 0 indicates that the request happens in the main frame; a positive value indicates the ID of a subframe in which the request happens. If the document of a (sub-)frame is loaded (<code>type</code> is <code>main_frame</code> or <code>sub_frame</code>), <code>frameId</code> indicates the ID of this frame, not the ID of the outer frame. Frame IDs are unique within a tab."},
               "parentFrameId": {"type": "integer", "description": "ID of frame that wraps the frame which sent the request. Set to -1 if no parent frame exists."},
+              "experimentalPostData": {

[Matt Perry, 2012/07/23 21:19:01]

Drop the "experimental" prefix. We're moving away from that convention.

[battre, 2012/07/24 09:28:53]

Don't you want to indicate to developers that this feature may change? I am
concerned that we might not get it right in the first try.

[Matt Perry, 2012/07/24 20:46:57]

The description indicates that. Also, the feature is restricted to the dev
channel. I think that's enough, and is the convention we're moving towards.

[vabr (Chromium), 2012/07/30 16:05:57]

I removed the 'experimental' prefix based on the above discussion.

+                "type": "object",
+                "optional": true,
+                "description": "Experimental feature. Container for representations of data sent by the request via POST method. Only provided if extraInfoSpec contains requestPostData.",
+                "properties": {
+                  "formData": {
+                    "type": "object",
+                    "optional": true,
+                    "description": "If the POST data is a sequence of key-value pairs, either in multipart/form-data, or application/x-www-form-urlencoded, this dictionary is present and for each key contains the list of all values for that key. If the data is in another encoding, or if it was malformed, the dictionary is not present. It is also not present if the form upload was chunked. Example value of this dictionary is {'key': ['value1', 'value2']}.",
+                    "properties": {},
+                    "additionalProperties": {
+                      "type": "array",
+                      "items": { "type": "string" }
+                    }
+                  }
+                }
+              },
               "tabId": {"type": "integer", "description": "The ID of the tab in which the request takes place. Set to -1 if the request isn't related to a tab."},
               "type": {"type": "string", "enum": ["main_frame", "sub_frame", "stylesheet", "script", "image", "object", "xmlhttprequest", "other"], "description": "How the requested resource will be used."},
               "timeStamp": {"type": "number", "description": "The time when this signal is triggered, in milliseconds since the epoch."}
@@ -125,7 +142,7 @@
             "description": "Array of extra information that should be passed to the listener function.",
             "items": {
               "type": "string",
-              "enum": ["blocking"]
+              "enum": ["blocking", "requestPostData"]

[Matt Perry, 2012/07/23 21:19:01]

imo "request" is unnecessary here. There's only 1 kind of "postData", so I think
that would be a fine name.

[vabr (Chromium), 2012/07/30 16:05:57]

Done.

             }
           }
         ],