[security] Remove uploaded documents once the embedding is done #1637

Closed
opened 2025-11-11 14:48:55 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @leobenkel on GitHub (Jul 30, 2024).

Is your feature request related to a problem? Please describe.

Today, the back-end keep the documents uploaded. And for safety, that's not super clean.

Describe the solution you'd like

Would be nice to have the document uploaded, with obfuscated name. The embedding is done. Then the file is removed, no trace left.

Describe alternatives you've considered

Right now, I have to remove the file manually which is annoying.

Originally created by @leobenkel on GitHub (Jul 30, 2024). **Is your feature request related to a problem? Please describe.** Today, the back-end keep the documents uploaded. And for safety, that's not super clean. **Describe the solution you'd like** Would be nice to have the document uploaded, with obfuscated name. The embedding is done. Then the file is removed, no trace left. **Describe alternatives you've considered** Right now, I have to remove the file manually which is annoying.
Author
Owner

@leobenkel commented on GitHub (Jul 30, 2024):

why the closing without conversation ?

@leobenkel commented on GitHub (Jul 30, 2024): why the closing without conversation ?
Author
Owner

@justinh-rahb commented on GitHub (Jul 30, 2024):

@leobenkel we close issues that lack sufficient details for reproduction or resolution, or that don't follow our issue/feature request template. This helps us maintain clarity and ensures we can address valid concerns effectively. Thank you for understanding!

@justinh-rahb commented on GitHub (Jul 30, 2024): @leobenkel we close issues that lack sufficient details for reproduction or resolution, or that don't follow our issue/feature request template. This helps us maintain clarity and ensures we can address valid concerns effectively. Thank you for understanding!
Author
Owner

@leobenkel commented on GitHub (Jul 31, 2024):

@leobenkel we close issues that lack sufficient details for reproduction or resolution, or that don't follow our issue/feature request template. This helps us maintain clarity and ensures we can address valid concerns effectively. Thank you for understanding!

I followed the predefined pattern for feature request, what did i miss ?

@leobenkel commented on GitHub (Jul 31, 2024): > @leobenkel we close issues that lack sufficient details for reproduction or resolution, or that don't follow our issue/feature request template. This helps us maintain clarity and ensures we can address valid concerns effectively. Thank you for understanding! I followed the predefined pattern for feature request, what did i miss ?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#1637