CORS NGINX configuration problem

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have an Ubuntu web server with NGINX. I want to add CORS support for the following WebDAV methods: PUT, GET, OPTIONS, MKCOL, PROPFIND. I read couple of articles how to add the CORS support and I have put the following lines in /etc/nginx/sites-enabled/default:



server 
listen 80 default_server;
listen [::]:80 default_server;
# return 301 https://$server_name$request_uri;


root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location /
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;


location /test
add_header "Access-Control-Allow-Origin" *;
add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND';
add_header "Access-Control-Allow-Credentials" "true";
add_header "Access-Control-Allow-Headers" "Authorization, origin, accept";
add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range';
dav_methods PUT DELETE MKCOL;
dav_ext_methods PROPFIND OPTIONS;
autoindex on;
create_full_put_path on;
limit_except GET HEAD
allow XXX.XXX.XXX.XXX/32;
deny all;





But even after restart the nginx server the client is complaining that the CORS is not enabled. I got error messages that "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'XXXX.com' is therefore not allowed access. The response had HTTP status code 404.". The interesting part is that I don't get such errors when the file is present, only if it is not there, but on the other hand I am testing the same on another server and on this server when the file is not present I got only HTTP status code 404.



And this is my nginx version and installed modules:



$ nginx -V
nginx version: nginx/1.10.3 (Ubuntu)
built with OpenSSL 1.0.2g 1 Mar 2016
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_v2_module --with-http_sub_module --with-http_xslt_module --with-stream --with-stream_ssl_module --with-mail --with-mail_ssl_module --with-threads --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-auth-pam --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-dav-ext-module --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-echo --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-upstream-fair --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/ngx_http_substitutions_filter_module


[EDIT]


This is the output of curl



$ curl --head http://ip_address/test:
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 10 Oct 2017 10:02:23 GMT
Content-Type: text/html
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization, origin, accept
Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range


So it looks all good but I still got this errors in the developer console.










share|improve this question























  • my testing shows the add_header directives are working. try adding the output of a curl request to your question. e.g. curl --head <yourhost>/test
    – the_velour_fog
    Oct 10 '17 at 9:52










  • @the_velour_fog I have added the output of curl in my original thread at the end, check for the text after Edit. It seems all OK to me but still I got these error messages.
    – Georgе Stoyanov
    Oct 10 '17 at 10:06










  • yeah, so to me it looks like the error is in the browser. I dont see how GETs would be a problem. are you preflighting your CORs for POST requests?
    – the_velour_fog
    Oct 10 '17 at 10:24










  • @the_velour_fog I don't do anything like this. So I am trying to build an MPEG-DASH origin server and I got this error when I try to play the content over some of the web players. The strange thing is that I got these errors when the player cannot fetch some chunk from my origin server but doesn't show this error when it is not able to fetch a chunk from some of the CDN based origin servers, so I was wondering what could be the reason for this error.
    – Georgе Stoyanov
    Oct 10 '17 at 10:34














up vote
0
down vote

favorite












I have an Ubuntu web server with NGINX. I want to add CORS support for the following WebDAV methods: PUT, GET, OPTIONS, MKCOL, PROPFIND. I read couple of articles how to add the CORS support and I have put the following lines in /etc/nginx/sites-enabled/default:



server 
listen 80 default_server;
listen [::]:80 default_server;
# return 301 https://$server_name$request_uri;


root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location /
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;


location /test
add_header "Access-Control-Allow-Origin" *;
add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND';
add_header "Access-Control-Allow-Credentials" "true";
add_header "Access-Control-Allow-Headers" "Authorization, origin, accept";
add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range';
dav_methods PUT DELETE MKCOL;
dav_ext_methods PROPFIND OPTIONS;
autoindex on;
create_full_put_path on;
limit_except GET HEAD
allow XXX.XXX.XXX.XXX/32;
deny all;





But even after restart the nginx server the client is complaining that the CORS is not enabled. I got error messages that "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'XXXX.com' is therefore not allowed access. The response had HTTP status code 404.". The interesting part is that I don't get such errors when the file is present, only if it is not there, but on the other hand I am testing the same on another server and on this server when the file is not present I got only HTTP status code 404.



And this is my nginx version and installed modules:



$ nginx -V
nginx version: nginx/1.10.3 (Ubuntu)
built with OpenSSL 1.0.2g 1 Mar 2016
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_v2_module --with-http_sub_module --with-http_xslt_module --with-stream --with-stream_ssl_module --with-mail --with-mail_ssl_module --with-threads --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-auth-pam --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-dav-ext-module --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-echo --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-upstream-fair --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/ngx_http_substitutions_filter_module


[EDIT]


This is the output of curl



$ curl --head http://ip_address/test:
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 10 Oct 2017 10:02:23 GMT
Content-Type: text/html
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization, origin, accept
Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range


So it looks all good but I still got this errors in the developer console.










share|improve this question























  • my testing shows the add_header directives are working. try adding the output of a curl request to your question. e.g. curl --head <yourhost>/test
    – the_velour_fog
    Oct 10 '17 at 9:52










  • @the_velour_fog I have added the output of curl in my original thread at the end, check for the text after Edit. It seems all OK to me but still I got these error messages.
    – Georgе Stoyanov
    Oct 10 '17 at 10:06










  • yeah, so to me it looks like the error is in the browser. I dont see how GETs would be a problem. are you preflighting your CORs for POST requests?
    – the_velour_fog
    Oct 10 '17 at 10:24










  • @the_velour_fog I don't do anything like this. So I am trying to build an MPEG-DASH origin server and I got this error when I try to play the content over some of the web players. The strange thing is that I got these errors when the player cannot fetch some chunk from my origin server but doesn't show this error when it is not able to fetch a chunk from some of the CDN based origin servers, so I was wondering what could be the reason for this error.
    – Georgе Stoyanov
    Oct 10 '17 at 10:34












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have an Ubuntu web server with NGINX. I want to add CORS support for the following WebDAV methods: PUT, GET, OPTIONS, MKCOL, PROPFIND. I read couple of articles how to add the CORS support and I have put the following lines in /etc/nginx/sites-enabled/default:



server 
listen 80 default_server;
listen [::]:80 default_server;
# return 301 https://$server_name$request_uri;


root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location /
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;


location /test
add_header "Access-Control-Allow-Origin" *;
add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND';
add_header "Access-Control-Allow-Credentials" "true";
add_header "Access-Control-Allow-Headers" "Authorization, origin, accept";
add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range';
dav_methods PUT DELETE MKCOL;
dav_ext_methods PROPFIND OPTIONS;
autoindex on;
create_full_put_path on;
limit_except GET HEAD
allow XXX.XXX.XXX.XXX/32;
deny all;





But even after restart the nginx server the client is complaining that the CORS is not enabled. I got error messages that "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'XXXX.com' is therefore not allowed access. The response had HTTP status code 404.". The interesting part is that I don't get such errors when the file is present, only if it is not there, but on the other hand I am testing the same on another server and on this server when the file is not present I got only HTTP status code 404.



And this is my nginx version and installed modules:



$ nginx -V
nginx version: nginx/1.10.3 (Ubuntu)
built with OpenSSL 1.0.2g 1 Mar 2016
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_v2_module --with-http_sub_module --with-http_xslt_module --with-stream --with-stream_ssl_module --with-mail --with-mail_ssl_module --with-threads --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-auth-pam --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-dav-ext-module --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-echo --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-upstream-fair --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/ngx_http_substitutions_filter_module


[EDIT]


This is the output of curl



$ curl --head http://ip_address/test:
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 10 Oct 2017 10:02:23 GMT
Content-Type: text/html
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization, origin, accept
Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range


So it looks all good but I still got this errors in the developer console.










share|improve this question















I have an Ubuntu web server with NGINX. I want to add CORS support for the following WebDAV methods: PUT, GET, OPTIONS, MKCOL, PROPFIND. I read couple of articles how to add the CORS support and I have put the following lines in /etc/nginx/sites-enabled/default:



server 
listen 80 default_server;
listen [::]:80 default_server;
# return 301 https://$server_name$request_uri;


root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location /
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;


location /test
add_header "Access-Control-Allow-Origin" *;
add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND';
add_header "Access-Control-Allow-Credentials" "true";
add_header "Access-Control-Allow-Headers" "Authorization, origin, accept";
add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range';
dav_methods PUT DELETE MKCOL;
dav_ext_methods PROPFIND OPTIONS;
autoindex on;
create_full_put_path on;
limit_except GET HEAD
allow XXX.XXX.XXX.XXX/32;
deny all;





But even after restart the nginx server the client is complaining that the CORS is not enabled. I got error messages that "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'XXXX.com' is therefore not allowed access. The response had HTTP status code 404.". The interesting part is that I don't get such errors when the file is present, only if it is not there, but on the other hand I am testing the same on another server and on this server when the file is not present I got only HTTP status code 404.



And this is my nginx version and installed modules:



$ nginx -V
nginx version: nginx/1.10.3 (Ubuntu)
built with OpenSSL 1.0.2g 1 Mar 2016
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_v2_module --with-http_sub_module --with-http_xslt_module --with-stream --with-stream_ssl_module --with-mail --with-mail_ssl_module --with-threads --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-auth-pam --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-dav-ext-module --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-echo --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/nginx-upstream-fair --add-module=/build/nginx-Q158zN/nginx-1.10.3/debian/modules/ngx_http_substitutions_filter_module


[EDIT]


This is the output of curl



$ curl --head http://ip_address/test:
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 10 Oct 2017 10:02:23 GMT
Content-Type: text/html
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, OPTIONS, PUT, DELETE, MKCOL, PROPFIND
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Authorization, origin, accept
Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range


So it looks all good but I still got this errors in the developer console.







linux ubuntu nginx http






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 10 '17 at 10:05

























asked Oct 10 '17 at 7:37









Georgе Stoyanov

16515




16515











  • my testing shows the add_header directives are working. try adding the output of a curl request to your question. e.g. curl --head <yourhost>/test
    – the_velour_fog
    Oct 10 '17 at 9:52










  • @the_velour_fog I have added the output of curl in my original thread at the end, check for the text after Edit. It seems all OK to me but still I got these error messages.
    – Georgе Stoyanov
    Oct 10 '17 at 10:06










  • yeah, so to me it looks like the error is in the browser. I dont see how GETs would be a problem. are you preflighting your CORs for POST requests?
    – the_velour_fog
    Oct 10 '17 at 10:24










  • @the_velour_fog I don't do anything like this. So I am trying to build an MPEG-DASH origin server and I got this error when I try to play the content over some of the web players. The strange thing is that I got these errors when the player cannot fetch some chunk from my origin server but doesn't show this error when it is not able to fetch a chunk from some of the CDN based origin servers, so I was wondering what could be the reason for this error.
    – Georgе Stoyanov
    Oct 10 '17 at 10:34
















  • my testing shows the add_header directives are working. try adding the output of a curl request to your question. e.g. curl --head <yourhost>/test
    – the_velour_fog
    Oct 10 '17 at 9:52










  • @the_velour_fog I have added the output of curl in my original thread at the end, check for the text after Edit. It seems all OK to me but still I got these error messages.
    – Georgе Stoyanov
    Oct 10 '17 at 10:06










  • yeah, so to me it looks like the error is in the browser. I dont see how GETs would be a problem. are you preflighting your CORs for POST requests?
    – the_velour_fog
    Oct 10 '17 at 10:24










  • @the_velour_fog I don't do anything like this. So I am trying to build an MPEG-DASH origin server and I got this error when I try to play the content over some of the web players. The strange thing is that I got these errors when the player cannot fetch some chunk from my origin server but doesn't show this error when it is not able to fetch a chunk from some of the CDN based origin servers, so I was wondering what could be the reason for this error.
    – Georgе Stoyanov
    Oct 10 '17 at 10:34















my testing shows the add_header directives are working. try adding the output of a curl request to your question. e.g. curl --head <yourhost>/test
– the_velour_fog
Oct 10 '17 at 9:52




my testing shows the add_header directives are working. try adding the output of a curl request to your question. e.g. curl --head <yourhost>/test
– the_velour_fog
Oct 10 '17 at 9:52












@the_velour_fog I have added the output of curl in my original thread at the end, check for the text after Edit. It seems all OK to me but still I got these error messages.
– Georgе Stoyanov
Oct 10 '17 at 10:06




@the_velour_fog I have added the output of curl in my original thread at the end, check for the text after Edit. It seems all OK to me but still I got these error messages.
– Georgе Stoyanov
Oct 10 '17 at 10:06












yeah, so to me it looks like the error is in the browser. I dont see how GETs would be a problem. are you preflighting your CORs for POST requests?
– the_velour_fog
Oct 10 '17 at 10:24




yeah, so to me it looks like the error is in the browser. I dont see how GETs would be a problem. are you preflighting your CORs for POST requests?
– the_velour_fog
Oct 10 '17 at 10:24












@the_velour_fog I don't do anything like this. So I am trying to build an MPEG-DASH origin server and I got this error when I try to play the content over some of the web players. The strange thing is that I got these errors when the player cannot fetch some chunk from my origin server but doesn't show this error when it is not able to fetch a chunk from some of the CDN based origin servers, so I was wondering what could be the reason for this error.
– Georgе Stoyanov
Oct 10 '17 at 10:34




@the_velour_fog I don't do anything like this. So I am trying to build an MPEG-DASH origin server and I got this error when I try to play the content over some of the web players. The strange thing is that I got these errors when the player cannot fetch some chunk from my origin server but doesn't show this error when it is not able to fetch a chunk from some of the CDN based origin servers, so I was wondering what could be the reason for this error.
– Georgе Stoyanov
Oct 10 '17 at 10:34















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397182%2fcors-nginx-configuration-problem%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397182%2fcors-nginx-configuration-problem%23new-answer', 'question_page');

);

Post as a guest













































































wPjpTuPNVIiyh2tve Ffv2yKr6QUdUVt9eQimqz9vRLH 3ikQs uqe
jQzR7 HenP7ENi8keTqRG1FUnPX99 6Ih3c7zaO rehELTgDtNaMvqiRg97k8z qZ1tM,jXuKKANxm,cCw,X 4QDvG

Popular posts from this blog

How to check contact read email or not when send email to Individual?

How many registers does an x86_64 CPU actually have?

Displaying single band from multi-band raster using QGIS