Hi, we updated GoodData-CN to 3.7 but I am not abl...
# gooddata-cn
Hi, we updated GoodData-CN to 3.7 but I am not able to update UI libraries. I only found this "old" article
Compatibility with <http://GoodData.CN|GoodData.CN>
https://sdk.gooddata.com/gooddata-ui/docs/supported_versions.html#compatibility-with-gooddatacn. What version should I use for CN 3.7?
I tried 9.9 but it is not working due to cors errros.
...has been blocked by CORS policy: Request header field pragma is not allowed by Access-Control-Allow-Headers in preflight response.
Hi Jakub, CORS issue should be solved by following below page: https://www.gooddata.com/docs/cloud-native/3.7/manage-organization/set-up-cors-for-organization/ Can you please give it a try and let us know if it helped?
Hi, thank you for the link. I have no problem with
but with
. Can I also configure headers from settings?
Do you know which GoodData UI version is best for GoodData CN 3.7?
For example api call on
• preflight (OPTIONS) works • It return this allowed headers.
Then is GET request on
and there is also
header. Which cause the cors error because
is not listed in allowed headers.
I assume it is because the UI library is not compatible with the backend version. But I do not know which version should I use.
I may not know all the details about our UI SDK but I would be a little bit surprised if the new version really started sending Pragma headers in HTTP requests since Pragma header is generally deprecated (it was designed for HTTP/1.0 and replaced by Cache-Control many years ago for HTTP/1.1+). Which tool or browser are you using for creating these HTTP request? (Perhaps it might be our Python SDK?) @Julius Kos No matter what, I believe it is safe to create an internal ticket for our CN team to add the
header to the
list in our CN codebase - there should be no downside to that (since Cache-Control is already allowed) but it would increase the compatibility with various HTTP agents. Thanks!
We do not fire/create those request, they are from the GoodData UI components. I see the Axios is used there.
A quick search over our UI SDK suggests we are only sending Pragma headers in E2E tests but I don't see it anywhere else. Axios library also does not seem to be sending it by default ... but there might some other dependencies involved (and I am not very good at reading JS/TS code). Nevertheless, I believe that the main problem is that our CN backend doesn't allow it right now in CORS and this should be fixed indeed.
👍 1