[SOLVED] Re: TW / Firefox - can't upload images to github issues anymore (CORS failure)
David C Rankin <[email protected]> Sat, 27 Jun 2026 17:29:34 -0500
| Newsgroups | gmane.linux.suse.general |
|---|---|
| Message-ID | <[email protected]> |
On 6/25/26 8:13 PM, OldTime85--- via openSUSE Users wrote:
> So I brought up the FF developer tools to look for errors, and I do
> get errors like:
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading
> the remote resource at
> https://github-production-user-asset-6210df.s3.amazonaws.com/. (Reason:
> CORS request did not succeed). Status code: (null).
>
> Uncaught AttachmentUploadError: App assets attachment upload failed:
> storage request.
> o attachment-upload.ts:63
> setTimeout handler*o attachment-upload.ts:62
> process attachment-upload.ts:104
> d batch-upload.ts:59
> 819435 file-attachment.ts:36
> m index.js:96
> attach index.js:164
> p index.js:246
> Caused by: error { isTrusted: true, lengthComputable: false, loaded: 0,
> total: 0, eventPhase: 0, bubbles: false, cancelable: false, returnValue:
> true, defaultPrevented: false, composed: false }
> attachment-upload.ts:63:35
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading
> the remote resource athttps://api.github.com/_private/browser/errors.
> (Reason: CORS request did not succeed). Status code: (null).
It was NoScript (well a github change that impacted NoScript).
What's changed, is that even if you set the shown github.com
addresses to "Trusted" in NoScript, when you attempt an upload an
additional github.co./aws-asset.... address appear that was not present
when you opened and began filling out the issue (or comment, etc..).
After going one-by-one through Ublock, Ghostery and then NoScript,
the additional links to the aws-assets.... location requiring javascript
was discovered.
This must have been a new change in the March (~90 day ago)
timeframe, because for the decade+ before using FF with NoScript had no
issues uploading images as long as the github.com/... urls shown when
visiting the site were set to "Trusted" (or "Temp Trusted") in NoScript.
Mystery solved.
--
David C. Rankin, J.D.,P.E.