Open Palollo opened 1 month ago
it's because keycloak is not yet initialized
Ok, keep going ;) It happens even when you refresh the page just after the a previous refresh (less than a minute). The token is still valid but it is no remembered. Refreshing the details page of a not public dataset... The first GET sent does not include the token, so an error 401 is received and thus that error message of the screen capture is shown. Then two more request (duplicated) are sent, as described also for the main page in #178.
This wath is shown when refreshing the page:
This is related to #178, because that page is also reloaded multiple times: in the first load that false error is shown but later the page is refreshed again and then the error disappears. So maybe the fix for the previous issue fixes that one also.