CORS header 'Access-Control-Allow-Origin' missing #71

New issue

Closed

opened 2025-12-28 18:00:03 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:00:03 +00:00

Owner

Originally created by @mike-petrov on GitHub (Mar 21, 2024).

Originally assigned to: @smallhive on GitHub.

Current Behavior

Request GET https://rest.fs.neo.org/v1/auth/bearer?walletConnect=true with bearer and signatures headers being blocked by browser because of "CORS Missing Allow Origin":

Expected Behavior

Panel working fine.

Steps to Reproduce

Can be reproduced with panel.fs.neo.org if you're to sign an object operations token.

Context

panel.fs.neo.org is broken because of this.

Regression

Yes, 0.7.2 handled this fine.

Your Environment

Version of the product used: 0.8.1

Originally created by @mike-petrov on GitHub (Mar 21, 2024). Originally assigned to: @smallhive on GitHub. ## Current Behavior Request `GET https://rest.fs.neo.org/v1/auth/bearer?walletConnect=true` with bearer and signatures headers being blocked by browser because of "CORS Missing Allow Origin": <img width="300" alt="image" src="https://github.com/nspcc-dev/neofs-rest-gw/assets/32885629/d82216f8-daf6-4e66-95b5-b665cd773338"> related to https://github.com/nspcc-dev/neofs-rest-gw/issues/166 ## Expected Behavior Panel working fine. ## Steps to Reproduce Can be reproduced with panel.fs.neo.org if you're to sign an object operations token. ## Context panel.fs.neo.org is broken because of this. ## Regression Yes, 0.7.2 handled this fine. ## Your Environment * Version of the product used: 0.8.1