Branched ~ 198281 ~ Authorization Header Not Received by Service During File Upload Operation

Hi,


On the version v34.1.31if the token contains a dot (e.g. "

eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJuYW1laWQiOiIyIiw

") then the header is totally removed.


Regards,

Julien


3 Replies 1 reply marked as answer

PS Praveen Sellappan Syncfusion Team July 27, 2026 05:44 PM UTC

Hi Julien,

Greetings from Syncfusion support.

Based on the information provided, we have validated and classified the reported scenario “Authorization Header Not Received by Service During File Upload Operation” as a bug on our end. The fix for this issue will be included in the upcoming weekly release scheduled for August 4,2026. 
You can track the status of the fix using the following link:

Disclaimer: Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works of reprioritization.
Regards,
Praveen


PS Praveen Sellappan Syncfusion Team August 5, 2026 12:15 PM UTC

Hi Julien,

Thank you for your patience.
We regret to inform you that we will not be able to include the fix for the reported issue in this week's patch release as previously communicated. Due to the complexity of the issue, we require additional time to complete the implementation and perform thorough validation to ensure a reliable and high-quality fix.
We would like to update you that the fix is currently in the testing phase and is planned for inclusion in the upcoming weekly patch release scheduled for August 11, 2026.
We sincerely apologize for the delay and appreciate your understanding. Thank you for your continued support and patience while we work toward resolving this issue.
Regards,
Praveen


PS Praveen Sellappan Syncfusion Team August 12, 2026 10:06 AM UTC

Hi Julien,

 

Thanks for your patience.

  

We are pleased to inform you that our weekly patch release has been successfully rolled out, and the issue "Authorization Header Not Received by Service During File Upload Operation" has been resolved in this release.


To access this fix, we suggest updating the package to version 34.2.3. We have also included a sample in the latest version for your reference.

Sample: Attached as a ZIP file.


Feedback:  File Manager upload does not send authorization header when JWT bearer token contains a dot in Blazor | Feedback Portal



Root Cause: The upload feature was sending duplicate authorization headers due to the way headers were handled between the File Manager and Uploader components. Earlier fixes prevented duplicate headers but unintentionally caused valid JWT bearer tokens to be removed before upload requests were sent. As a result, upload requests reached the service without the required authorization header, leading to authentication failures.

We thank you for your support and appreciate your patience while waiting for this release. Please get in touch with us if you require any further assistance.

 

Regards,

Praveen Sellappan


Attachment: FileManagerSample_c52a9fe7.zip

Marked as answer
Loader.
Up arrow icon