使用UrlFetchApp的POST请求返回404，其中等效curl成功(POST request using UrlFetchApp returns 404 where equivalent cur

使用UrlFetchApp的POST请求返回404，其中等效curl成功(POST request using UrlFetchApp returns 404 where equivalent curl succeeds)

我有一个冗长的卷曲请求，我想使用UrlFetchApp模拟：

curl 'https://example.com/index.php' -H 'Cookie: "XXXXXXXXXX"' -H 'Origin: https://example.com' -H 'Accept-Encoding: gzip, deflate' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36' -H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryK0ckVcd9Rae277Ae' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8' -H 'Cache-Control: max-age=0' -H 'Referer: https://example.com/index.php' -H 'Connection: keep-alive' --data-binary $'------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="user"\r\n\r\nstaff\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="name"\r\n\r\nJohn Smith\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="staffid"\r\n\r\ne00000\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="preferred"\r\n\r\nEmail\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="phone"\r\n\r\n9999 9999\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="altemail"\r\n\r\njohn.smith@example.com\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="subject"\r\n\r\nother\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="desc"\r\n\r\nTEST ONLY.\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="userfield"\r\n\r\n\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="timezone"\r\n\r\nMon Mar 23 2015 10:28:33 GMT+1100 (AEDT)\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="browserstring"\r\n\r\nMozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="files[]"; filename=""\r\nContent-Type: application/octet-stream\r\n\r\n\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae--\r\n' --compressed

我正在使用以下UrlFetchApp代码，它只是创建一个有效负载和一个头对象，并将有效负载编码为二进制blob：

虽然我已经修改了一些细节以匿名化示例（包括删除cookie详细信息），但这两个请求应该是相同的。 curl请求有效，UrlFetchApp请求是根据curl请求的复制构建的。但是UrlFetchApp请求返回404。

我很想知道我是否错过了任何明显的东西。

I have a lengthy curl request that I'd like to emulate using UrlFetchApp:

curl 'https://example.com/index.php' -H 'Cookie: "XXXXXXXXXX"' -H 'Origin: https://example.com' -H 'Accept-Encoding: gzip, deflate' -H 'Accept-Language: en-US,en;q=0.8' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36' -H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryK0ckVcd9Rae277Ae' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8' -H 'Cache-Control: max-age=0' -H 'Referer: https://example.com/index.php' -H 'Connection: keep-alive' --data-binary $'------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="user"\r\n\r\nstaff\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="name"\r\n\r\nJohn Smith\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="staffid"\r\n\r\ne00000\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="preferred"\r\n\r\nEmail\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="phone"\r\n\r\n9999 9999\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="altemail"\r\n\r\njohn.smith@example.com\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="subject"\r\n\r\nother\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="desc"\r\n\r\nTEST ONLY.\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="userfield"\r\n\r\n\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="timezone"\r\n\r\nMon Mar 23 2015 10:28:33 GMT+1100 (AEDT)\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="browserstring"\r\n\r\nMozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae\r\nContent-Disposition: form-data; name="files[]"; filename=""\r\nContent-Type: application/octet-stream\r\n\r\n\r\n------WebKitFormBoundaryK0ckVcd9Rae277Ae--\r\n' --compressed

I'm using the following UrlFetchApp code, which simply creates a payload and a header object, and encodes the payload as a binary blob:

While I've altered some of the details in order to anonymise the example (including removing the cookie details), the two requests should be identical. The curl request works, and the UrlFetchApp request is constructed based on copying from the curl request. But the UrlFetchApp request returns 404.

I'd be keen to know if I've missed anything obvious.

最满意答案

您正在定义'reqHeaders'但使用'reqHeadersMin'。

你说这是一个PUT，但我没有在curl命令中看到-X PUT，所以我认为它默认为GET。并且您将fetch（）调用定义为选项中的POST。

Turns out the problem here relates to firewalls.

In the instance where this didn't work, the UrlFetchApp target was behind a firewall. The curl command worked where this was sent from a terminal on a machine within that firewall. However, Google's Apps Script servers are outside that firewall, and hence the UrlFetchApp request fails.

更多推荐