You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should rather return a 403, and allow downloading the file after authentication - and in password useless case (Issue #29), it should directly deliver the file.
And the management console, in the "Objects" tab, should link each sha to download the file.
Let me know your remarks about that, I can (try to) implement it in a PR.
The text was updated successfully, but these errors were encountered:
Got an eye in the code (and got it back, it helps)
In fact, there's a 404 because mux routes check the Accept header.
So, I well understood, - in the current state of the app - there is to :
add a generic route handler which catches anything not having the correct Accept Header
Hi, thanks for the LFS-mechanism, that's great !
If I try to download an object directly with its url - the one I read in the , I got a 404.
http://localhost:8080/_user_/repo/objects/_sha_
It should rather return a 403, and allow downloading the file after authentication - and in password useless case (Issue #29), it should directly deliver the file.
And the management console, in the "Objects" tab, should link each sha to download the file.
Let me know your remarks about that, I can (try to) implement it in a PR.
The text was updated successfully, but these errors were encountered: