Fix 401 by using adminApi instead of raw axios#468
Merged
sahilds1 merged 1 commit intoCodeForPhilly:developfrom Feb 26, 2026
Merged
Fix 401 by using adminApi instead of raw axios#468sahilds1 merged 1 commit intoCodeForPhilly:developfrom
sahilds1 merged 1 commit intoCodeForPhilly:developfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
File uploads were resulting in
401 Unauthorized.This was becauase
UploadFile.tsxwas using a rawaxios.post()call instead of theadminApiclient, so no JWT Authorization header was being sent with upload requests.uploadFilePOST requests require authentication, so uploads were failing with 401.@sahilds1 I tried your suggested fix and it worked. I was able to upload a file.
To reiterate the fix, I replaced
axios.post()withadminApi.post(), which automatically attaches the JWT token via its request interceptor.I also removed the explicit
Content-Type: multipart/form-dataheader since Axios auto-sets it (with the required boundary parameter) when the body is aFormData.Related Issue
Closes #467
Also may close #390, but I'm not sure
Manual Tests
I manually tested these changes by uploading a pdf and confirming successful upload with 201
Reviewers
@sahilds1 @taichan03
Notes
This might fix the 2nd error in issue #390, but would want to manually test with the original file to see if the error is still happening.