-
Notifications
You must be signed in to change notification settings - Fork 4
SSL certificate problem with json2veris [NEW FEATURE REQUEST: migrate RCurl code to httr] #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you paste a dump of |
locale: attached base packages: other attached packages: loaded via a namespace (and not attached): |
Roger that. Thx. I figured it was Windows. The |
Here is my workaround. Requires you download "ca-bundle.crt"library(verisr) On Fri, Jan 23, 2015 at 2:14 PM, boB Rudis notifications@github.com wrote:
|
(We're in the middle of a big report prep, so I'm leaving the main repo alone). I changed from |
Hi. I tried loading your version but am still getting Error in function (type, msg, asError = TRUE) : when I try
Not sure if that's supposed to happen or not. The workaround juk80x posted does work for me with the master branch and this fork. When I tried using already downloaded files locally with
that did work. |
thx for testing! (I need to get a non-locked down Windows VM up soon). Give |
Glad to help! Same outcome:
doesn't work but
does (after I manually copied a ca-bundle.crt file into my working directory. This then does work with local json files
|
When json2veris attempts to pull down the schema it gives the following error:
Error in function (type, msg, asError = TRUE) :
SSL certificate problem: unable to get local issuer certificate
I attempted to pull down the schema manually using a getURL call that includes a 'cainfo' parameter. I then used the same fromJSON call to get the schema. But when I passed it in using the 'schema' paramter in json2veris I received another error.
Error in readLines(file, warn = FALSE) : 'con' is not a connection
Unfortunately that is the extent of my R knowledge.
The text was updated successfully, but these errors were encountered: