-
Notifications
You must be signed in to change notification settings - Fork 180
Cross-Origin Read Blocking (CORB) blocked cross-origin response thredds #1335
Comments
Hi again all, My JavaScript code:
The result:
Can anyone help me to solve this problem? Cheers, Mostafa |
It is quite possible that the CORS settings from tomcat and the CORS settings in the TDS are interfering with each other. I would recommend not using the TDS CORS settings and putting them in place higher in the stack, such as in Tomcat. As always, when dealing with CORS in production, make sure to consult the person or group in charge of the network and domain on how best it should be implemented. Having CORS headers show up on network scans without notice usually leads to bad times. |
Hi dear,
I have an issue about cros.
I tried to get this link using ajax (http://192.168.229.94:8080/thredds/wms/testAll/GFS202009060000?service=WMS&version=1.3.0&REQUEST=GetMetadata&item=minmax&LAYERS=HGT&SRS=EPSG%3A4326&BBOX=50.4,38,56.8,44.4&WIDTH=256&HEIGHT=256&callback=jQuery3410787186710990256_1599400222381&_=1599400222382)
But I've got the following error:
I added the following line in the usr/local/tds/tomcat/conf/web.xml
Also I did uncomment the the following line in the /usr/local/tds/tomcat/content/thredds/threddsconfig.xml
But I receive this error again.
How can I solve my issue.
Thanks
The text was updated successfully, but these errors were encountered: