Skip to content
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

Optionaly proxify images src with atmos/camo #781

Merged
merged 4 commits into from
Sep 1, 2016
Merged

Optionaly proxify images src with atmos/camo #781

merged 4 commits into from
Sep 1, 2016

Conversation

luxifer
Copy link
Contributor

@luxifer luxifer commented Jun 22, 2016

I used selfoss every day with a Let's Encrypt certificate but the connection is not fully encrypted when some feeds have images that does not come from https. To address this situation I used https://github.com/atmos/camo (an http proxy to serve images through SSL). It's optional so if the configuration for host and key are empty, nothing is done.

Add option to proxify img src when feeds are not https. requires a
running server of https://github.com/atmos/camo
@niol
Copy link
Collaborator

niol commented Jun 23, 2016

This looks very useful, thanks.

But is seems to be a lot of code for something that could be implemented using a htmLawed hook and some f3 standard functions.

@luxifer
Copy link
Contributor Author

luxifer commented Jun 23, 2016

I'll check this out and rewrite my PR to be shorter and leaner. This was a
proof of concept. Thanks for the insight.

Florent Viel
Le 23 juin 2016 11:05 AM, "niol" [email protected] a écrit :

This looks very useful, thanks.

But is seems to be a lot of code for something that could be implemented
using a htmLawed hook and some f3 standard functions.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#781 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAZlBtp_EDT_t36l4a7DGjTVK7dWGlVeks5qOkxqgaJpZM4I7uCm
.

@jtojnar
Copy link
Member

jtojnar commented Jun 23, 2016

I like it the way it is implemented here, separation of concerns-wise.

@SSilence SSilence merged commit fec279b into fossar:master Sep 1, 2016
@jtojnar
Copy link
Member

jtojnar commented Sep 27, 2020

Hi @luxifer. Previously, it was not clear if selfoss was licensed under GPL 3 only, or also any later version. Could you clarify whether you are fine with licensing your contribution under GPL-3-or-later?

Thanks again and sorry for the confusion.

@luxifer
Copy link
Contributor Author

luxifer commented Sep 27, 2020

I'm fine with GPL-3 licensing

@jtojnar
Copy link
Member

jtojnar commented Sep 27, 2020

@luxifer Unfortunately, the fact that GPL 3 is ambiguous (as described in https://gnu.org/licenses/identify-licenses-clearly.html) is the whole reason for the uncertainty. Could you please clarify whether you are okay with GPL-3-or-later rather than GPL-3-only specifically?

@luxifer
Copy link
Contributor Author

luxifer commented Sep 27, 2020

Sorry for the confusion but I'm fine with any licensing ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants