When using the eodag-labextension with jupyterhub v4.1, it shows the following error at the start of jupyterlab :
And there is nothing in the providers list as shown in the following screenshot :
When sending again the requests that fail and show a 403 code using the network console in the browser they show a 200 code but the issue remains.
Using the reload button inside the extension shows the same error as when starting jupyterlab.
When using the network console to send back the request it set the "Sec-Fetch-Mode" to "no-cors" and it shows a 200 code but the requests that show a 403 code has the "Sec-Fetch-Mode" to "cors".
This issue does not appear when using jupyterhub v3.1
This issue does not appear when building in local mode, it only appears when spawning through a jupyterhub server
When using the eodag-labextension with jupyterhub v4.1, it shows the following error at the start of jupyterlab :
And there is nothing in the providers list as shown in the following screenshot :
When sending again the requests that fail and show a 403 code using the network console in the browser they show a 200 code but the issue remains. Using the reload button inside the extension shows the same error as when starting jupyterlab. When using the network console to send back the request it set the "Sec-Fetch-Mode" to "no-cors" and it shows a 200 code but the requests that show a 403 code has the "Sec-Fetch-Mode" to "cors".
This issue does not appear when using jupyterhub v3.1 This issue does not appear when building in local mode, it only appears when spawning through a jupyterhub server