Skip to content

http remote: check and handle properly access denied and other HTTP codes #2510

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.

Sign up for GitHub

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

Jump to bottom
Closed
shcheklein opened this issue Sep 17, 2019 · 2 comments · Fixed by #2794
Closed

http remote: check and handle properly access denied and other HTTP codes #2510

shcheklein opened this issue Sep 17, 2019 · 2 comments · Fixed by #2794
Assignees
@pared
Labels
bug Did we break something? p1-important Important, aka current backlog of things to do

Comments

@shcheklein
Copy link
Member

Looks like when HTTP remote can't return an object and returns access denied we consider it the same way as 404 and don't even mention this to user.
@efiop efiop added bug Did we break something? p2-medium Medium priority, should be done, but less important p1-important Important, aka current backlog of things to do and removed p2-medium Medium priority, should be done, but less important labels Sep 19, 2019
@efiop
Copy link
Contributor

efiop commented Oct 1, 2019

@shcheklein Are you talking about dvc pull from http remote? Or something else?

@shcheklein
Copy link
Member Author

@efiop yep, it was dvc pull/dvc fetch.

@pared pared self-assigned this Nov 13, 2019
@pared pared mentioned this issue Nov 14, 2019
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pared pared

Labels
bug Did we break something? p1-important Important, aka current backlog of things to do
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

remote: http: raise exception when response with error status code pared/dvc
3 participants
@shcheklein @efiop @pared