Files
openobserve/web
Bhargav 5d05004e69 fix: redirect to login page on unauthorised error with http2 streaming (#8185)
### **PR Type**
Bug fix, Enhancement


___

### **Description**
- Handle non-JSON error responses safely

- Redirect on 401 during stream reading

- Preserve normal AbortError behavior


___

### Diagram Walkthrough


```mermaid
flowchart LR
  req["HTTP streaming request"] -- "response.ok" --> ok["Process stream with worker"]
  req -- "not ok (error)" --> parseErr["Try parse JSON error"]
  parseErr -- "success" --> onErr["onError(traceId, payload)"]
  parseErr -- "fail" --> throwResp["Throw raw response"]
  stream["Read stream loop"] -- "AbortError" --> ignore["Ignore, expected cancel"]
  stream -- "status === 401" --> redirect["Logout, clear storage, reload"]
  stream -- "other error" --> logOnError["console.error + onError"]
```



<details> <summary><h3> File Walkthrough</h3></summary>

<table><thead><tr><th></th><th align="left">Relevant
files</th></tr></thead><tbody><tr><td><strong>Bug
fix</strong></td><td><table>
<tr>
  <td>
    <details>
<summary><strong>useStreamingSearch.ts</strong><dd><code>Safer error
parsing and 401 redirect in streaming</code>&nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; </dd></summary>
<hr>

web/src/composables/useStreamingSearch.ts

<ul><li>Wrap non-ok response handling in try/catch.<br> <li> Throw raw
response if JSON parsing fails.<br> <li> On stream read errors, handle
401 by logout/clear/reload.<br> <li> Keep AbortError ignored; log and
propagate other errors.</ul>


</details>


  </td>
<td><a
href="https://github.com/openobserve/openobserve/pull/8185/files#diff-8fce3e25a161cd458e734bd9b1f98aadefe3482da7b6529a5b1f4fa20ec115e2">+14/-5</a>&nbsp;
&nbsp; </td>

</tr>
</table></td></tr></tr></tbody></table>

</details>

___
2025-08-29 13:09:55 +05:30
..
2023-02-02 09:03:11 +05:30
2023-08-06 01:29:13 +08:00
2023-02-02 09:03:11 +05:30
2023-02-02 09:03:11 +05:30
2023-02-02 09:03:11 +05:30
2025-08-11 17:06:35 -07:00
2024-04-03 12:49:25 +05:30
2023-02-02 09:03:11 +05:30

web

This template should help get you started developing with Vue 3 in Vite.

VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).

Type Support for .vue Imports in TS

TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:

  1. Disable the built-in TypeScript Extension
    1. Run Extensions: Show Built-in Extensions from VSCode's command palette
    2. Find TypeScript and JavaScript Language Features, right click and select Disable (Workspace)
  2. Reload the VSCode window by running Developer: Reload Window from the command palette.

Customize configuration

See Vite Configuration Reference.

Project Setup

npm install

Compile and Hot-Reload for Development

For stand-alone UI development environment, create .env file and which contains below environment variable

VITE_OPENOBSERVE_ENDPOINT=http://localhost:5080/
npm run dev

Type-Check, Compile and Minify for Production

npm run build

Run Unit Tests with Vitest

npm run test:unit

Run End-to-End Tests with Cypress

npm run test:e2e:dev

This runs the end-to-end tests against the Vite development server. It is much faster than the production build.

But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):

npm run build
npm run test:e2e

Lint with ESLint

npm run lint