You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The root endpoint provides the URL of the log cache in the key "log_cache", but the code accesses it with the key "log-cache", never returning the correct value.
There is a fallback which uses the api-endpoint and replaces any occurrence of "api" with "log-cache". This works in most of the cases, but not if the letters "api" are part of the remaining URL.
The text was updated successfully, but these errors were encountered:
I am not sure what the correct failure behavior should be for the fallback case:
a) replace "api" only if it is right after "https://", at the start of the URL and throw an exception if it is not found there.
b) replace "api" only if it is right after "https://", at the start of the URL and return the unchanged URL if no replacement happens (current behavior).
The root endpoint provides the URL of the log cache in the key "log_cache", but the code accesses it with the key "log-cache", never returning the correct value.
There is a fallback which uses the api-endpoint and replaces any occurrence of "api" with "log-cache". This works in most of the cases, but not if the letters "api" are part of the remaining URL.
The text was updated successfully, but these errors were encountered: