Please let me know if you need any additional information. > No 'Access-Control-Allow-Origin' header is present on the requested > nginx: configuration file /etc/nginx/nf test is successful > nginx: the configuration file /etc/nginx/nf syntax is ok ![]() Enter Access-Control-Allow-Origin as the header name. In the Custom HTTP headers section, click Add. Right click the site you want to enable CORS for and go to Properties. > fastcgi_pass unix:/run/php-fpm/www.sock Open Internet Information Service (IIS) Manager. > # Else this rewrite block wouldn't be needed (GlobalRedirect) > # Some modules enforce no slash (/) at the end of the URL > * add_header 'Access-Control-Allow-Origin' 'origin-list' * > # This is cool because no php is touched for static content > *add_header 'Access-Control-Allow-Origin' 'origin-list' * > # Load configuration files for the default server block. > add_header Strict-Transport-Security "max-age=63072000" always ![]() > # HSTS (ngx_http_headers_module is required) (63072000 seconds) For what it's worth for future readers with a similar problem, I found that my node.js server was passing an Access-Control-Allow-Origin: '' header for some reason, as well as the actual header I'd set in node.js to restrict CORS. > ssl_certificate /etc/ssl/fullchain1.pem ssl_certificate_key It could be that the server behind your proxypass was setting the Access-Control-Allow-Origin header as well. > root /var/www/html/devportal-v2/developer_portal/web ![]() The drupal Nginx config (/etc/nginx/conf.d/nf) I have added *add_header 'Access-Control-Allow-Origin' 'origin-list' * in > You might want the "add_header" line there instead. > location, there is no Access-Control-Allow-Origin header added. > In your "drupal" nginx config, if the request is handled in the "php" > No ‘Access-Control-Allow-Origin’ header is present on the requested On Thu, at 12:50:34PM +0530, Kaushal Shriyan wrote:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |