You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error I'm getting back looking at the console logs is this:
[Error] Failed to load resource: An SSL error has occurred and a secure connection to the server cannot be made. (got-issuer_live.json, line 0)
on this request copied from the browser network requests:
curl 'https://www.blockcerts.org:80/mockissuer/issuer/got-issuer_live.json' \
-XGET \
-H 'Origin: https://www.blockcerts.org' \
-H 'Accept: */*' \
-H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15' \
-H 'Referer: https://www.blockcerts.org/'
Seems to be related to the :80 that is being added on, probably since the link is a non-https link, and probably being redirected to the https equivalent but with the :80 appended? Taking off the :80 works.
The text was updated successfully, but these errors were encountered:
ghost
pushed a commit
that referenced
this issue
Aug 7, 2018
https://community.blockcerts.org/t/inconsistent-signed-json-examples-between-repos/1248
This cert (https://raw.githubusercontent.com/blockchain-certificates/cert-web-component/master/demo/sample_signed_cert-valid-1.2.0.json) does not validate on blockcerts.org but apparently validates with the cert-web-component.
The error I'm getting back looking at the console logs is this:
on this request copied from the browser network requests:
Seems to be related to the
:80
that is being added on, probably since the link is a non-https link, and probably being redirected to the https equivalent but with the:80
appended? Taking off the:80
works.The text was updated successfully, but these errors were encountered: