Skip to content
This repository has been archived by the owner on Oct 6, 2024. It is now read-only.

Add support for private repositories #62

Closed
mitar opened this issue Apr 23, 2015 · 6 comments
Closed

Add support for private repositories #62

mitar opened this issue Apr 23, 2015 · 6 comments

Comments

@mitar
Copy link

mitar commented Apr 23, 2015

When I access a private raw file in GitHub, GitHub appends a token to the URL so that one can acess it:

https://raw.githubusercontent.com/...?token=...

When I open rawgit URL I get 404. :-(

It seems token is not used/passed on?

I would need this to be able to add SVG images to the README in a private repository.

@rgrove
Copy link
Owner

rgrove commented Apr 23, 2015

Sorry, private repos are intentionally not supported because I don't want peoples' tokens flowing through RawGit (or the CDN). That's too much scary responsibility!

Feel free to fork RawGit and run a private instance that adds that functionality though.

@mitar
Copy link
Author

mitar commented Apr 23, 2015

Oh. But you could just display a warning once somebody pastes in a link with a token? No? That this is insecure. And aren't tokens per-file anyway?

Hm, you could at least display an error in this case. And not strange 404.

@rgrove
Copy link
Owner

rgrove commented Apr 23, 2015

Good idea. I'll consider adding a special error.

@nzec
Copy link

nzec commented Jan 17, 2018

@rgrove Any plans for this?

@rgrove
Copy link
Owner

rgrove commented Jan 17, 2018

Still no plans to support private repos. Especially now, since people have recently been trying to use RawGit to distribute malware. The last thing I need is malware hosted in a private repo that I can't see.

@ErShakirAnsari
Copy link

ErShakirAnsari commented Mar 11, 2019

Can we NOW access a private repo's raw file using private access token in url?

Repository owner locked as resolved and limited conversation to collaborators Mar 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants