System fails to process E2B R2/R3 files when file extension is in uppercase
Before:
When an otherwise valid E2B R2/R3 file was uploaded with an uppercase extension (for example, xyz.XML), the system did not recognize the file type. As a result, the file remained unclassified and was not processed further. (38282046)
After:
The system accepts and correctly processes valid E2B R2/R3 files regardless of whether the file extension is in lowercase (.xml) or uppercase (.XML).
Impacted Areas:
E2B Intake across all ingestion routes:
- Manual Upload
- sFTP (Interchange Service)
- REST API
Parent topic: What's fixed