Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork880
Description
If you use knit2wp to a site that has good transport-security configuration--meaning it doesn't permit obsolete transport-security protocols--you will get an error. By "obsolete transport security", I mean any transport-security protocol other than TLS 1.2 or 1.3 (more info).
The ultimate problem is with the RCurl package, which this function depends on for data-transport. The error can reliably be reproduced with a trivial example, such asRCurl::getURL("http://www.arencambre.com/").
The below sites will produce an error. They are verified athttps://gf.dev/tls-scanner as not supporting anything lower than TLS 1.2:
- https://www.smu.edu/
- https://www.rstudio.com/
- https://www.arencambre.com/
- https://en.wikipedia.com/
- https://www.harvard.edu/
Note that knit2wp depends on these packages:
- RWordPress (latest commit is August 2012)
- XMLRPC, which RWordPress uses to interact with WordPress.
- RCurl, which XMLRPC uses for the actual communications with WordPress. Arelevant issue was reported to RCurl in November 2018, but there is no apparent action on it. I also opened amore general issue, similar to this one.
By filing an issue to this repo, I promise that
- I have fully read the issue guide athttps://yihui.org/issue/.
- I have provided the necessary information about my issue.
- If I'm asking a question, I have already asked it on Stack Overflow or RStudio Community, waited for at least 24 hours, and included a link to my question there.
- If I'm filing a bug report, I have included a minimal, self-contained, and reproducible example, and have also included
xfun::session_info('knitr'). I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version:remotes::install_github('yihui/knitr'). - If I have posted the same issue elsewhere, I have also mentioned it in this issue.
- I have learned the Github Markdown syntax, and formatted my issue correctly.
I understand that my issue may be closed if I don't fulfill my promises.