When making a call to a URL with an ampersand it replaces the & with &

[tslape]

While making a call that contains an ampersand in the signed URL from S3, it replaces the & with & amp ; causing a 403 forbidden error.

The URL is being set in a Javascript function afterReponse from the previous call.

[MosayebG]

I have this issue too.

[hassy]

Do you have a reproducible test case?

[tslape]

{
    "config": {
        "target": "https://www.facebook.com",
        "timeout": 9,
        "phases": [
            {"duration": 1, "arrivalRate":1}
        ],
        "processor": "./MyFunctions.js"
    },
    "headers": {
    },
    "scenarios": [
        {
            "flow": [
                {
                    "get":{
                        "beforeRequest": "setJSONBody",
                        "url": "/GitHub/photos/a.395084243927205.1073741825.262588213843476/839624966139795/?type=1&theater",
                        "afterResponse": "setURL"
                    }
                },
                {
                    "get":{
                        "beforeRequest": "setJSONBody",
                        "url": "{{ url }}",
                        "afterResponse": "response"
                    }
                }
            ]
        }
    ]
}

module.exports = {
    setJSONBody: setJSONBody,
    setURL: setURL,
    response: response
}

function setJSONBody(requestParams, context, ee, next) {
    return next(); // MUST be called for the scenario to continue
}

function setURL(requestParams, response, context, ee, next) {
    console.log(requestParams.uri)
    context.vars['url']= '/GitHub/photos/a.395084243927205.1073741825.262588213843476/839624966139795/?type=1&theater';
    return next(); // MUST be called for the scenario to continue
}


function response(requestParams, response, context, ee, next) {
    console.log(requestParams.uri)
    return next(); // MUST be called for the scenario to continue
}

The console will display

\https://www.facebook.com/GitHub/photos/a.395084243927205.1073741825.262588213843476/839624966139795/?type=1&theater
 |https://www.facebook.com/GitHub/photos/a.395084243927205.1073741825.262588213843476/839624966139795/?type=1&theater

Facebook does not have an issue with the ampersand being encoded but it was where I was able to get a URL that had one. The issue occurs internally with files that are in S3 and have signed URLs and AWS does not view the encoded value as valid.

[hassy]

Thanks @tslape. You can set requestParams.uri directly instead of using a template variable. If you need the variable, use {{{ url }}} to prevent it from being HTML-encoded.

[tslape]

Thank you @hassy, using {{{ url }}} worked to prevent the encoding.

It may be useful to add this into the documents in the "Advanced: writing custom logic in Javascript" section.

[hassy]

Fixed in artilleryio/artillery-core#139