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

Bug: If a URL download does not have a Filename, he item is cached but can never be returned. #40

Open
SimonDarksideJ opened this issue Dec 18, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@SimonDarksideJ
Copy link
Contributor

Reality Collective - Utilities Bug Report

Describe the bug

If a URL download does not have a Filename, he item is cached but can never be returned.

To Reproduce

  1. Call "download" against an endpoint that returns a stream (e.g. HTTP://server/getfile/5823C048-89BE-4513-83C6-E6713A85D50E)
  2. Try to download the file again
  3. File reports as Exists, but cannot be found.

Expected behavior

If a file is downloaded and cached, it should be returned from the cache correctly.

Actual behavior

File reports that it exists in cache but then cannot be found when loading

Additional context

The issue is centred around the fact that the File download and File exists checks return two difference style paths for the BytesDownload call. All System.IO checks should NOT have a "file://" prefix and must be stripped.

@SimonDarksideJ SimonDarksideJ added the bug Something isn't working label Dec 18, 2023
SimonDarksideJ added a commit that referenced this issue Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant