Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.1.4
-
Untriaged
-
0
-
Yes
Description
This is a very simplified version of code that I am using within our Customer 360 function to retrieve data from Jira. The code below works in 6.6 but fails with a 404 in 7.1. As far as I can tell so far, the issue has to do with how the curl command is encoding (or not?) some of the characters such as '+' and possibly '=':
function OnUpdate(doc, meta) {
|
const path ="search?jql=project+=+MB+AND+type+=+Improvement"
|
const response = curl('GET', url_jira, {path:path+'&startAt=' + '0' + '&maxResults=' + '1000'});
|
log(response)
|
}
|
The url_jira binding points to 'https://issues.couchbase.com/rest/api/latest/' and the above path is accessible without any authentication.
Issue | Resolution |
A server regression in version 7.1.2 might have caused a cURL request encoding issue. | The default behavior has now been reverted to that in version 7.1.0. In addition, there’s now an optional argument, "url_encode_version", with potential values of [6.6.2, 7.1.0, and 7.2.0]. This argument facilitates the selection of an encoding scheme during upgrades if necessary. |
Attachments
For Gerrit Dashboard: MB-57138 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
191884,4 | MB-57138 : Introduce url_encode_version to handle curl request encoding behaviour | 7.1.x | eventing-ee | Status: MERGED | +2 | +1 |
191885,3 | MB-57138 : Introduce url_encode_version to handle curl request encoding behaviour | 7.1.x | eventing | Status: MERGED | +2 | +1 |