Widget: initial request returns NULL objects:

[TarmoKlaarRIA]

tested 22.08.2023, env: dev.buerokratt.ee

Following request reutrns null object with statuscode 300:
https://ruuter.dev.buerokratt.ee/pub2/get-widget-config
{
"response": null
}
https://ruuter.dev.buerokratt.ee/pub2/get-emergency-notice
{
"response": null
}
https://ruuter.dev.buerokratt.ee/pub1/custom-jwt-userinfo
{
"data": {
"custom_jwt_userinfo": null
},
"error": null
}

[1AhmedYasser]

273.mov

Working on the local side as shown in the video, needs to be rechecked on the dev environment

As for the custom_jwt_userinfo returning null, its normal because in order for this endpoint to return the data the user should be logged in, but here is using the chat bot anonymously, so when the user logs in the clientCustomJwtCookie is filled and used in custom_jwt_userinfo endpoint

[TarmoKlaarRIA]

https://dev.buerokratt.ee/
Loading widget configuration works once and then doesn't work again. This morning the configuration was loaded, and the appearance of the widget changed. At the moment the tests show http.300 again and the color remains blue.
And another question, why is the configuration loading 2 times?

[rasmusei]

@turnerrainer, take a look at Ahmeds comment:
There are 2 things that could be added as a fix

1- Disable Caching on Module index.html by adding (Not Recommended)

2- Control Caching on API's in Java in case of ruuter via HTTP Headers (Recommended)
a- https://stackoverflow.com/questions/51524633/reactjs-how-to-prevent-browser-from-caching-static-files
b- https://stackoverflow.com/questions/49547/how-do-we-control-web-page-caching-across-all-browsers

In java:

response.setHeader("Cache-Control", "no-cache, no-store, must-revalidate"); // HTTP 1.1.
response.setHeader("Pragma", "no-cache"); // HTTP 1.0.
response.setHeader("Expires", "0"); // Proxies.

What do you think is more appropriate to use in our modules ?

Note: For example in chatbot when trying to set the cache control header to the api requests it stopped working, so i think Ruuter needs to account for this headers when needed

[rasmusei]

@turnerrainer still waiting your comment

[turnerrainer]

@rasmusei @1AhmedYasser
We'll solve it via buerokratt/Ruuter#213. Ruuter enhancement, not a Chatbot bug.

[turnerrainer]

Should be resolved by Ruuter v1 -> Ruuter v2 migration. Will be fully resolved by #213