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

support HTTP Redirect in server and provider #253

Closed
karma-sun opened this issue Apr 24, 2022 · 5 comments
Closed

support HTTP Redirect in server and provider #253

karma-sun opened this issue Apr 24, 2022 · 5 comments
Labels

Comments

@karma-sun
Copy link

Describe the bug
sometimes we need to provide a resource at external URL and let client request that URL directly,but send_resource method of server do not provide support for HTTP Redirect

@karma-sun karma-sun added the bug label Apr 24, 2022
@mar10 mar10 removed the bug label Apr 24, 2022
@mar10
Copy link
Owner

mar10 commented Apr 24, 2022

Thank you for contributing! 👍

In order to process your issue, we need some more information, explanation what already was tried and/or concrete data.

@karma-sun
Copy link
Author

karma-sun commented Apr 25, 2022

I tried to extend DAVNonCollection:

class MyDAVNonCollection(DAVNonCollection):

def get_content(self):
    # here I have a URL point to file in external server and want client to request it directly
    # but get_content() need return a file object
    # it is not good for me to open the file URL and return data, because the file is very large(may be 1GB or more)

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@yarikoptic
Copy link
Contributor

@karma-sun have you at the end found how to implement such redirection? (wsgidav newbee here, still orienting myself)

@karma-sun
Copy link
Author

@karma-sun have you at the end found how to implement such redirection? (wsgidav newbee here, still orienting myself)

no,I think the library must support it at first

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

No branches or pull requests

3 participants