n1k0 / readable-proxy Goto Github PK

And the server should be responsible of constructing a JSON error response out of it.

Admittedly I don't know too much about the differences in JSDOM and PhantomJS. But I see the app runs really slowly. So I made a version that uses JSDOM and it runs a lot faster and doesn't make my Macbook fan kick in. Mine doesn't support most of the options right now cause I just wanted to shoehorn in JSDOM to see if there was a performance improvement or not and there is. Here is the repo:

https://github.com/OKNoah/readable-proxy-jsdom

Is there some reason this uses PhantomJS and not JSDOM?

I tried creating node js application on OpenShift and provided the link to this repo as source but it doesn't work. The application won't start. What can I do?

This would help with debugging during development.

This would be useful for testing how things will work on Android vs. desktop Firefox.

For obvious performance reasons.

stdout maxBuffer exceeded
Sorry to bother you,
but I have no idea if that is coming form the proxy or the Readable.js lib,
or if I can raise that buffer limit somehow.
The website I tried: http://www.equestriadaily.com/2016/10/music-intersekt-twilight-says-bass-house.html

What can I do?

Follow-up to #15 (comments)

The URL is https://streams.spec.whatwg.org/

It fails at

Maybe Phantom can't cope with modern HTTPS setups?

Refs mozilla/readability#16 (comment)

I was running into the same "Unable to access" errors other users have reported. I eventually realized that the 1000 ms timeout value in phantom-scrape.js was just too low for any page I was hitting and my internet connection.

I'd like to bump the timeout value to at least 5000 ms, and add a handler so the app returns a more useful message.