-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
WIP Adding proxying support #40
Conversation
This is a great and useful feature! |
Sorry for not responding back earlier. When the server is started with DOWNLOAD_MODE=proxy, it's supposed to almost behave the same. However, there are two main differences: with current non-proxy mode:
with proxy-mode:
The main difference here would be that the icon binary will be sent over the request instead of being redirected to there. |
Thanks @karl-ravn for this contribution and sorry for getting back so late :( I, too, think this is useful for some people. Some suggestion before we merge:
|
Ok, I've done 1,2 and 4 but writing a good unit test for this... it's a bit tricky since I'm not really a Go developer.. |
I've just found this project searching for a favicon proxy, this PR would be so great to have :) |
Thanks @karl-ravn for adding this feature. I'm going to add a test and will release a new version soon, too. |
@mat is there any way to access this var when using the docker image? It appears its not currently available, and I don't see |
@csandman Good catch, I failed to release a new version of the Docker image! The |
Sometimes this service needs to be hidden behind friendly lines and not exposing the exact URL for the favicon resource that was requested. Sometimes you get mixed results when your own service runs https but the favicon is supposed to be downloaded from http - causing everything to break and emit errors.
Running the server with
DOWNLOAD_MODE=proxy
makes the server download and forward the resource to the user.