OPS for subscribed row data
Posted: Fri Jul 03, 2015 3:47 pm
Hi,
I have a problem when trying to download the paid DOCDB data (in zip format) to our remote server via wget or curl. I tried to use access token key in the header (OPS but probably it does not work for raw files), and also tried to submit cookie file after logged in (https://publication.epo.org/raw-data/au ... n?action=2) with our username and password. Both did not work. I have the below error. Any help would be greatly appreciated.
PS. an example data file link I use to download is something like: "https://publication.epo.org/raw-data/download/....zip".
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Best
I have a problem when trying to download the paid DOCDB data (in zip format) to our remote server via wget or curl. I tried to use access token key in the header (OPS but probably it does not work for raw files), and also tried to submit cookie file after logged in (https://publication.epo.org/raw-data/au ... n?action=2) with our username and password. Both did not work. I have the below error. Any help would be greatly appreciated.
PS. an example data file link I use to download is something like: "https://publication.epo.org/raw-data/download/....zip".
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Best