Skip to content
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

https error #1

Closed
subblue opened this issue Jul 13, 2015 · 6 comments
Closed

https error #1

subblue opened this issue Jul 13, 2015 · 6 comments

Comments

@subblue
Copy link

subblue commented Jul 13, 2015

I thought I'd give the script a quick spin with the gfx-resources example:

gh-readme-scrape mattdesl/graphics-resources gfx-resources/ -e pdf,pptx,ppt --rename

but got this error:

Searching 114 links
Error requesting URL: http://www.amazon.ca/Math-Primer-Graphics-Development-Edition/dp/1568817231
Error requesting URL: http://www.amazon.ca/Essential-Mathematics-Games-Interactive-Applications/dp/0123742978
_http_client.js:75
    throw new Error('Protocol "' + protocol + '" not supported. ' +
          ^
Error: Protocol "https:" not supported. Expected "http:".
    at new ClientRequest (_http_client.js:75:11)
    at Object.exports.request (http.js:49:10)
    at Object.exports.request (https.js:136:15)
    at get (/Users/tom/.nvm/versions/node/v0.12.0/lib/node_modules/gh-readme-scrape/node_modules/got/index.js:137:16)
    at ClientRequest.<anonymous> (/Users/tom/.nvm/versions/node/v0.12.0/lib/node_modules/gh-readme-scrape/node_modules/got/index.js:162:5)
    at ClientRequest.g (events.js:199:16)
    at ClientRequest.emit (events.js:129:20)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:419:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:111:23)
    at Socket.socketOnData (_http_client.js:310:20)

thx

@mattdesl
Copy link
Owner

Hmm weird, I can't seem to reproduce it. I will poke around and see what I can do.

@mattdesl
Copy link
Owner

Hey Tom, when you run node -v and npm -v what are you getting?

There is another issue indicating this might be a problem with a particular version of node: TooTallNate/node-proxy-agent#1

@mattdesl
Copy link
Owner

OK, I actually just bumped my Node.js version and now I'm able to reproduce. 😄 Will continue digging...

@subblue
Copy link
Author

subblue commented Jul 14, 2015

Yeah I'm on node 0.12.0 at the moment, but switching back to 0.10.x via NVM it works ok.

@mattdesl
Copy link
Owner

If you re-install globally it should work now. This was fixed upstream: sindresorhus/got#80

@subblue
Copy link
Author

subblue commented Jul 15, 2015

Seems good now, thanks :)

@subblue subblue closed this as completed Jul 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants