[GH-ISSUE #4513] [BUG]: File Parsing Fails for URLs Without Explicit File Extensions #2869

Closed
opened 2026-02-22 18:31:36 -05:00 by yindo · 1 comment
Owner

Originally created by @angelplusultra on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4513

Originally assigned to: @timothycarambat on GitHub.

How are you running AnythingLLM?

All versions

What happened?

When attempting to pull and parse a file using either the RAG Modal or @agent mode, the process fails if the URL does not explicitly end with a file extension (e.g., .pdf, .csv). This occurs even when the server responds with a correct Content-Type header that identifies the file type.

Example:

The following URL fails to be processed, despite responding with an application/pdf content type:

https://arxiv.org/pdf/2307.10265

Observed Behavior:

The application logs display the following error:


[2] Error processing single file File extension .10265 not supported for parsing and cannot be assumed as text file type.

This error originates from the file extension guard located at:

https://github.com/Mintplex-Labs/anything-llm/blob/89a01492b51a23150b59732166b90ebdd1843c50/collector/processSingleFile/index.js#L58-L72

Expected Behavior:

The system should be able to successfully pull and parse files from URLs that do not explicitly contain a file extension, provided the Content-Type header in the server's response clearly indicates the file's MIME type.


Are there known steps to reproduce?

No response

Originally created by @angelplusultra on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4513 Originally assigned to: @timothycarambat on GitHub. ### How are you running AnythingLLM? All versions ### What happened? When attempting to pull and parse a file using either the RAG Modal or `@agent` mode, the process fails if the URL does not explicitly end with a file extension (e.g., `.pdf`, `.csv`). This occurs even when the server responds with a correct `Content-Type` header that identifies the file type. **Example:** The following URL fails to be processed, despite responding with an `application/pdf` content type: https://arxiv.org/pdf/2307.10265 **Observed Behavior:** The application logs display the following error: ``` [2] Error processing single file File extension .10265 not supported for parsing and cannot be assumed as text file type. ``` This error originates from the file extension guard located at: https://github.com/Mintplex-Labs/anything-llm/blob/89a01492b51a23150b59732166b90ebdd1843c50/collector/processSingleFile/index.js#L58-L72 **Expected Behavior:** The system should be able to successfully pull and parse files from URLs that do not explicitly contain a file extension, provided the `Content-Type` header in the server's response clearly indicates the file's MIME type. --- ### Are there known steps to reproduce? _No response_
yindo added the bugpossible bug labels 2026-02-22 18:31:36 -05:00
Author
Owner

@Guru6163 commented on GitHub (Oct 8, 2025):

I would like to work on this @timothycarambat

@Guru6163 commented on GitHub (Oct 8, 2025): I would like to work on this @timothycarambat
yindo changed title from [BUG]: File Parsing Fails for URLs Without Explicit File Extensions to [GH-ISSUE #4513] [BUG]: File Parsing Fails for URLs Without Explicit File Extensions 2026-06-05 14:49:00 -04:00
yindo closed this issue 2026-06-05 14:49:00 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2869