Fix Nginx CORS Header Conflict -- 2
Budget: ₹600 – ₹1,500 INR
The store at store.binjabbar.com is throwing the classic browser error:
“has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header contains multiple values ‘*, *’, but only one is allowed.”
I run the site on my own VPS and have full access to every Nginx conf file as well as any included snippets. Only GET requests are affected; POSTs and other verbs return cleanly. I’m looking for someone who can:
• trace where the duplicate Access-Control-Allow-Origin header is being injected (Nginx main block, a location block, proxy_pass response, or a stray add_header statement)
• adjust the configuration so the header is set once, with the correct value, and survives reloads and certificate renewals
• verify the fix in the browser console and via curl so GET calls succeed without CORS complaints
No code changes are required on the application side; this is purely an Nginx configuration task. I will provide SSH access immediately after awarding so you can test, reload, and—once we both confirm the error is gone—sign off.
“has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header contains multiple values ‘*, *’, but only one is allowed.”
I run the site on my own VPS and have full access to every Nginx conf file as well as any included snippets. Only GET requests are affected; POSTs and other verbs return cleanly. I’m looking for someone who can:
• trace where the duplicate Access-Control-Allow-Origin header is being injected (Nginx main block, a location block, proxy_pass response, or a stray add_header statement)
• adjust the configuration so the header is set once, with the correct value, and survives reloads and certificate renewals
• verify the fix in the browser console and via curl so GET calls succeed without CORS complaints
No code changes are required on the application side; this is purely an Nginx configuration task. I will provide SSH access immediately after awarding so you can test, reload, and—once we both confirm the error is gone—sign off.