* webui: allow viewing conversations and sending messages even if llama-server is down - Cached llama.cpp server properties in browser localStorage on startup, persisting successful fetches and reloading them when refresh attempts fail so the chat UI continues to render while the backend is unavailable. - Cleared the stored server properties when resetting the store to prevent stale capability data after cache-backed operation. - Kept the original error-splash behavior when no cached props exist so fresh installs still surface a clear failure state instead of rendering stale data. * feat: Add UI for `props` endpoint unavailable + cleanup logic * webui: extend cached props fallback to offline errors Treat connection failures (refused, DNS, timeout, fetch) the same way as server 5xx so the warning banner shows up when cache is available, instead of falling back to a full error screen. * webui: Left the chat form enabled when a server warning is present so operators can keep sending messages e.g., to restart the backend over llama-swap, even while cached /props data is in use * chore: update webui build output --------- Co-authored-by: Pascal <admin@serveurperso.com>
45 lines
1.1 KiB
TypeScript
45 lines
1.1 KiB
TypeScript
import { error } from '@sveltejs/kit';
|
|
import { browser } from '$app/environment';
|
|
import { config } from '$lib/stores/settings.svelte';
|
|
|
|
/**
|
|
* Validates API key by making a request to the server props endpoint
|
|
* Throws SvelteKit errors for authentication failures or server issues
|
|
*/
|
|
export async function validateApiKey(fetch: typeof globalThis.fetch): Promise<void> {
|
|
if (!browser) {
|
|
return;
|
|
}
|
|
|
|
try {
|
|
const apiKey = config().apiKey;
|
|
|
|
const headers: Record<string, string> = {
|
|
'Content-Type': 'application/json'
|
|
};
|
|
|
|
if (apiKey) {
|
|
headers.Authorization = `Bearer ${apiKey}`;
|
|
}
|
|
|
|
const response = await fetch(`./props`, { headers });
|
|
|
|
if (!response.ok) {
|
|
if (response.status === 401 || response.status === 403) {
|
|
throw error(401, 'Access denied');
|
|
}
|
|
|
|
console.warn(`Server responded with status ${response.status} during API key validation`);
|
|
return;
|
|
}
|
|
} catch (err) {
|
|
// If it's already a SvelteKit error, re-throw it
|
|
if (err && typeof err === 'object' && 'status' in err) {
|
|
throw err;
|
|
}
|
|
|
|
// Network or other errors
|
|
console.warn('Cannot connect to server for API key validation:', err);
|
|
}
|
|
}
|