Closed jmav closed 10 years ago
This seems like a reasonable feature. Currently, we support grunt@0.3
so I will have to look into compatibility. In the interim, you can use a function to generate a similar set of results:
function configureRequest(dest, url) {
return {
dest: dest,
src: {
url: url,
strictSSL: false
}
};
}
grunt.initConfig({
curl: {
url1: configureRequest('1.js', 'https://google.com/path/to/file.js')
}
});
Sorry for the delay on the follow-up. It looks like I will not be able to attend to this tonight. I will take another look by the end of next weekend.
Alright, so I have done my research and am deciding to not implement this for now. As suspected, grunt@0.4
are not compatible with the current src
/dest
syntax. As a result, any implementation would reproduce a lot of framework work which I am against.
I'm getting "Warning: UNABLE_TO_VERIFY_LEAF_SIGNATURE" because of the https certificate is not signed. Solution: option: rejectUnauthorized: false
I'm using Short format (dest: src) & have at least 30 files defined. It's not appropriate to use Long format for each file, it's very disturbing. I've tried with "curl-dir" but without luck. Please add global & subtask options for this kind of problems.
Thank You