readable-proxy icon indicating copy to clipboard operation
readable-proxy copied to clipboard

Node proxy server attempting to fetch readable contents from any provided URL.

Results 10 readable-proxy issues
Sort by recently updated
recently updated
newest added

default maxBuffer is 200K byte MAX_BUFFER=5242880 npm start take 5MB for maxBuffer related to #23

A better fix for #25, avoids putting anything other than JSON on stdout.

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...

`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...

Basically, I described the motivations in the commits. I'm not sure if it's a good idea to send all three commits in one pull request, I just don't know how...

Regarding #12, the new version of PhantomJS was no better in than the old one when it failed :) After playing around yesterday I have a number of patches that...

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?

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...

Refs https://github.com/mozilla/readability/issues/16#issuecomment-76982098

enhancement