ayastreb / bandwidth-hero-proxy Goto Github PK

After deploying the project on my own server, when i access some websites it doesn't load the images.
When i open the console and checked the network tab, i've seen 401 error code and cross-origin issue message, how to do in that case?

Hi @ayastreb ,
I think I would need API documentation (how to make request with postman, ...).
I would like to make another application that would use my bandwidth-hero-proxy as a mean of image compression. However, I am not good at nodejs to read the source code.

Anybody know what i'm doing wrong?

`/root/bandwidth-hero-proxy-master/src/proxy.js:14
...pick(req.headers, ['cookie', 'dnt', 'referer']),
^^^

SyntaxError: Unexpected token ...
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/root/bandwidth-hero-proxy-master/server.js:5:15)
`

"Convert to black and white" is on by default. I suggest changing this to "off", as few people will want their web pages in monochrome. Apart from that it is good.

This is a error I only met once, on my Ubuntu laptop. I use the same server that work on other of my machine (both Ubuntu and Windows, both firefox and chrome)

What happen:
Chrome, FIrefox on Ubuntu OS my laptop cannot get any image.
(Ubuntu on others machine worked, Windows on the same laptop worked)

When I check the console, it said:
Failed to load resource: the server responded with a status of 404 ()
With the url
http://206.189.84.191:26465/%20?url=http%3A%2F%2F206.189.84.191%3A26465%2F%2520%3Furl%3Dhttps%253A%252F%252Fi.imgur.com%252FaVfWYVl.jpg%26l%3D40&l=40

When I copy and paste the url on browser address bar, it say:
Cannot GET /%20

I am trying to host on AWS beantalk because heroku seem not to have enough RAM.
But I can't set HTTPS.

Youtobe video does not correspond to reality.
I don't know what to do.

any image that is embed not compressed can you fix it and thanks

Mixed Content: The page at 'https://github.com/ayastreb/bandwidth-hero-proxy' was loaded over HTTPS, but requested an insecure image 'http://206.189.84.191:26465/?url=https%3A%2F%2Fassets-cdn.github.com%2Fimages%2Fspinners%2Foctocat-spinner-128.gif&bw=0&l=40'. This request has been blocked; the content must be served over HTTPS.

I host on http://206.189.84.191:26465 (Dokku server without domain name) because I is somewhat expensive to buy (and time consuming to setup) a name domain.

Screenshot

By the way, Facebook work just fine.

Maybe that could be interesting to add this one

Hello,

I would like to adapt it for a php application on the server, but how it communicating with the chrome extension?
Maybe there is more possible to reduce and save traffic

i get this error when running the server
/root/boost/bandwidth-hero-proxy/src/proxy.js:14
...pick(req.headers, ['cookie', 'dnt', 'referer']),
^^^
SyntaxError: Unexpected token ...
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/root/boost/bandwidth-hero-proxy/server.js:6:15)

I have installed node.js and npm

Waterfox supports webp, but looks like webp compression has been removed entirely for firefox (waterfox has started showing black backgrounds after it didn't have that issue at all), I suggest keeping webp support but for waterfox ua only. Thanks.

Please add a simple file cache for frequently optimized images with a configurable size. Maybe you could use node-cache-manager with node-cache-manager-fs-binary?

According to the sharp JPEG output options, the default option is baseline, not progressive JPEG. Could you enable progressive and possibly optimiseScans as well for faster loading images? Thanks!

Hello, a newbie here

as Heroku service is no longer attainable for me, would someone kindly teach me how to self-host, please ?
i also read the manual but I am afraid I do not understand

thank you

It would be nice if every moving image was excluded or converted into WebM, for example.

To go even further, the user can choose how to deal with any type of image extension like .png .jpeg .gif etc. if he wants to.

Best regards
Snowy

Heja! It says "When active, Bandwidth Hero intercepts all images loading requests"
Does WEBP count too? (I think yes?) If yes would it not be nice to embed a setting to skip the request for them?

(Sorry I don't know much about programming/developing and all the stuff..)

Add on README.md simple instructions to run on Glitch.com

it doesn't work on manga or manhua websites on chapter page.
and thanks

The transparent background on some GIF and PNG images comes out as black, making many buttons hard to read. It would be better if the compression process was skipped for GIFs and PNGs (or at least for small ones, or those with transparent backgrounds).

Hey folks!

Are there any plans on providing a Docker image?

Hi,

does anyone have an updated Dockerfile by any chance?

The image from docker hub doesn't seem to work anymore.

I want to build this on ARM.

Thanks

its say in the log that:
! Push rejected, failed to compile Node.js app.
! Push failed

You can use Dokku on your own server to host bandwidth-hero-proxy. Worked as Heroku
https://github.com/dokku/dokku

Just create an app on Dokku

dokku apps:create bandwidth-hero-proxy # on dokku server

Then from your local PC, push the code to dokku

# on local laptop/pc
git add remote dokku dokku@your-server-ip:bandwidth-hero-proxy
git push dokku master 

Then check for port with

# on dokku server
dokku proxy:ports bandwidth-hero-proxy

your compression server is hosted at

http://your-server-ip:your-port/

Need to add ability to password protect the proxy server for users running their own private instance.