malformed CORS headers

20 views
Skip to first unread message

august black

unread,
Apr 1, 2026, 3:38:39 PMApr 1
to freeso...@googlegroups.com
Hi,

Thanks so much for all of the work going into Freesound.  It is such a lovely project and I so enjoy exploring the vast space of sound it holds!

I wanted to ask about some CORS errors I'm seeing lately (as of a few weeks ago)

has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header contains multiple values '*, *'

I believe the header value for 'Access-Control-Allow-Origin'  should only be "*" and not "*, *".

Thanks for the attention, best -August.

Frederic Font Corbera

unread,
Apr 4, 2026, 4:02:12 PMApr 4
to freeso...@googlegroups.com
Hi,

This looks like an issue derived of the change of infrastrucutre we carried out last week. We'll look into this and fix it. Thanks,

frederic


--
Frederic Font - ffont.github.io
Phonos - phonos.upf.edu
Music Technology Group, UPF - mtg.upf.edu
Freesound - freesound.org


--

---
You received this message because you are subscribed to the Google Groups "Freesound API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freesound-ap...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/freesound-api/CAHjm5xzWnVBru_Pse%2BkLTAaaRb6jK2BCKhh8QkjWF7Vo8TAOWQ%40mail.gmail.com.

Alastair Porter

unread,
Apr 7, 2026, 4:05:29 PMApr 7
to freeso...@googlegroups.com
Hi,
We've made a few changes to the network infrastructure for the recent move that we did. From what I can tell now we should have only one * in this header. Can you test again and confirm?

Alastair

On Wed, 1 Apr 2026 at 21:38, august black <augus...@gmail.com> wrote:
--

august black

unread,
Apr 7, 2026, 4:19:06 PMApr 7
to freeso...@googlegroups.com

yup, all is working again!

Thanks so much for the quick response and for the amazing freesound project.



Reply all
Reply to author
Forward
0 new messages