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

Support HTTP redirects for non-collection resources #1

Open
jwodder opened this issue Jan 8, 2024 · 0 comments
Open

Support HTTP redirects for non-collection resources #1

jwodder opened this issue Jan 8, 2024 · 0 comments
Labels
blocked Cannot be implemented until something else happens enhancement New feature or request therefor performance More efficient use of time and space

Comments

@jwodder
Copy link
Member

jwodder commented Jan 8, 2024

When a client GETs a blob asset or Zarr entry, the code currently "proxies" the request inefficiently by making a request for the actual resource on S3 and returning an fsspec IO object for use by wsgidav. Such GET requests should instead be responded to with HTTP redirects to the actual resources on S3.

Blocked by need for redirect support in wsgidav: mar10/wsgidav#311

  • If wsgidav fails to add the necessary features, alternative ways to get redirect support include:
    • Fork wsgidav and add the features ourselves
    • Find another Python WebDAV server library/framework that does support redirects
    • Write our own WebDAV server from (relatively speaking) scratch
      • If it came down to this, @jwodder would prefer to do it in Rust.
@jwodder jwodder added enhancement New feature or request therefor blocked Cannot be implemented until something else happens performance More efficient use of time and space labels Jan 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked Cannot be implemented until something else happens enhancement New feature or request therefor performance More efficient use of time and space
Projects
None yet
Development

No branches or pull requests

1 participant