After npm start node-unblocker throw errors. about node-unblocker HOT 11 CLOSED

Hey, sorry for the delay, I'm taking a look now

from node-unblocker.

@nfriedly Thanks!! Your app is awesome ;-)

from node-unblocker.

Hum.. it's working on my laptop (OS X). Did npm rebuild report any errors?

If not, then you can actually visit most websites without the iconv stuff - anything that's UTF-8 and even most text in other charsets will work without modification. To disable iconv, you currently have to do some edits to remove the encoding stuff` in https://github.com/nfriedly/node-unblocker/blob/master/lib/proxy.js: comment out line 9, 134, and 144, then combine lines 140 and 141 into something like this:

remote_response = remote_response.pipe(urlPrefixStream)

Let me know if that works for you.

from node-unblocker.

@nfriedly Thanks for respond I'll checkout soon. Thanks for your help!

from node-unblocker.

Hello!

@nfriedly thanks that helped me a lot :-) !

Unfortunately now when I run app in my localhost after fill the form I see

Gatling worker thread 1 up and listening
error RangeError: Maximum call stack size exceeded
    at String.replace (native)
    at rewriteUrls (/Users/mateusz/Desktop/node-unblocker/lib/urlprefixstream.js:45:19)
    at Stream.write (/Users/mateusz/Desktop/node-unblocker/lib/urlprefixstream.js:86:17)
    at Stream.stream.write (/Users/mateusz/Desktop/node-unblocker/node_modules/through/index.js:26:11)
    at Stream.ondata (stream.js:51:26)
    at Stream.emit (events.js:129:20)
    at drain (/Users/mateusz/Desktop/node-unblocker/node_modules/through/index.js:36:16)
    at Stream.stream.queue.stream.push (/Users/mateusz/Desktop/node-unblocker/node_modules/through/index.js:45:5)
    at Stream.write (/Users/mateusz/Desktop/node-unblocker/lib/urlprefixstream.js:89:14)
    at Stream.stream.write (/Users/mateusz/Desktop/node-unblocker/node_modules/through/index.js:26:11)
Error sending 500! Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:335:11)
    at ServerResponse.res.setHeader (/Users/mateusz/Desktop/node-unblocker/node_modules/connect/lib/patch.js:59:22)
    at Domain.<anonymous> (/Users/mateusz/Desktop/node-unblocker/node_modules/gatling/gatling.js:81:22)
    at Domain.emit (events.js:107:17)
    at Domain.errorHandler [as _errorHandler] (domain.js:102:19)
    at process._fatalException (node.js:233:33)
Gatling worker thread 3 up and listening

(null):0
(null)

RangeError: Maximum call stack size exceeded
Gatling worker thread 4 up and listening

any thoughts ? ;-)

from node-unblocker.

What version of node.js are you on? (Run node -v)

from node-unblocker.

Hello @nfriedly I'm using node v0.12.0 Hopefully this will be helpful ;-)

from node-unblocker.

Oh, yea, it is. I haven't worked on this in a while, so it hasn't been tested on the 0.12 releases. You could try updating to the latest (0.12.2), but if that doesn't fix it, then you might have to downgrade to 0.10.x - You can download old versions from http://nodejs.org/dist/ I thin http://nodejs.org/dist/v0.10.38/node-v0.10.38-darwin-x64.tar.gz is the one you'd need if 0.12.2 doesn't work.

Sorry about that. I'll work 0.12 support whenever I have the time, but it might be a little while. (This was originally written for node v0.4, so there's probably some cruft that just isn't supported anymore.)

from node-unblocker.

Oh thanks!! That's make sense. I'll try to fix that and create PR Thanks!!

from node-unblocker.

Btw, starting with unblocker v0.14, everything should compatible with node v0.12, and I also just put out a 1.0 release with some big changes. Please try out one of those and file a new bug if you run into any issues there.

from node-unblocker.

Of course I will thanks!!!!

from node-unblocker.