Ah, I can see why css/js could be an issue for some uses. I'm ... • Aaron Parecki

56°F

cactus https://github.com/cactus • Jul 4
go-camo was indeed originally intended to proxy only images, for two reasons: 1) the camo project it was inspired by only proxied images 2) my use-case at the time only required proxying of images

Later, a fork was created by a user to additionally proxy fonts and css. I wasn't comfortable including those in go-camo -- see discussion on https://github.com/cactus/go-camo/issues/20.

In my experience, video files are "usually" either linked (by url, no content warning), uploaded (service hosts it, so no content warning), or inlined from some hosting service (eg. youtube, vimeo; ssl provided by service). Video files are also generally much larger than image content.

Can you further describe your use-case/requirements for proxying video?

Ah, I can see why css/js could be an issue for some uses.

I'm using this on the server side of my new social reader application so that all image/video URLs presented to the reader apps are https and from the same origin. The videos come from either Instagram, Twitter, or peoples' own blogs hosting video files directly. Because the majority of the content is twitter-like short posts, the video files are normally always under a minute long so they aren't actually that big.

Portland, Oregon, USA • 78°F

Wed, Jul 4, 2018 2:02pm -07:00

Have you written a response to this? Let me know the URL:

Posted in /replies using quill.p3k.io